Transaction Details
Tx hash
dd3f70063010f424bad8de3d3151f8f6a3716cd8102ba2418fcd6f0cafbf8088
Tx prefix hash
843235a3a11ca8206fa2f6dd170e055443ac7cef4318b5682786e431363ec1ea
Tx public key
2ce91bcc55dd15cbe5ab389c5d2497ff726c6635a1e19b92fd04f3153a947b79
Age [y:d:h:m:s]
04:283:17:57:44
Timestamp [UCT] (epoch)
2019-09-29 23:42:47 (1569800567)
Block
274984 (1224636 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
012ce91bcc55dd15cbe5ab389c5d2497ff726c6635a1e19b92fd04f3153a947b7902110000012eaa9cfb43000000000000000000032100b3093aab91487872a3226f00371ab82b79b926e3e8e85860bf2b26699bab50aa
Outputs
1 output(s) for total of 20.176221371 ARQ
stealth address amount amount idx
00: 57041f26e57ba6929aa2b36378dc9eb84d115dd6a959cbed8764f279bfddfa4a 20.176221371 1235030 of 0

Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

        
          {
  "version": 2, 
  "unlock_time": 275002, 
  "vin": [ {
      "gen": {
        "height": 274984
      }
    }
  ], 
  "vout": [ {
      "amount": 20176221371, 
      "target": {
        "key": "57041f26e57ba6929aa2b36378dc9eb84d115dd6a959cbed8764f279bfddfa4a"
      }
    }
  ], 
  "extra": [ 1, 44, 233, 27, 204, 85, 221, 21, 203, 229, 171, 56, 156, 93, 36, 151, 255, 114, 108, 102, 53, 161, 225, 155, 146, 253, 4, 243, 21, 58, 148, 123, 121, 2, 17, 0, 0, 1, 46, 170, 156, 251, 67, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 179, 9, 58, 171, 145, 72, 120, 114, 163, 34, 111, 0, 55, 26, 184, 43, 121, 185, 38, 227, 232, 232, 88, 96, 191, 43, 38, 105, 155, 171, 80, 170
  ], 
  "rct_signatures": {
    "type": 0
  }
}