Transaction Details
Tx hash
df4c94ad773311469205bfa1f86511a877cd8e588ef2f58814e09268abcdd6e8
Tx prefix hash
a6a1e8d4ac2885af01f8c69cc97315512d2e0c07101a188d178fde91b2604601
Tx public key
410a7a4f4211fa9fd149020d514e27e5783c4b6b4f26bf0e4122af000cf17045
Age [y:d:h:m:s]
05:121:23:38:55
Timestamp [UCT] (epoch)
2019-07-31 14:06:57 (1564582017)
Block
232134 (1368480 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01410a7a4f4211fa9fd149020d514e27e5783c4b6b4f26bf0e4122af000cf170450211000000013dd6a500000000000000000000032100e9487d906991155c664c8a5356b58e2d177a178cfe2a080cdeda1e623b751f60
Outputs
1 output(s) for total of 18.142185819 ARQ
stealth address amount amount idx
00: 4e601faeaa78994e3f7413f6893a0060bf9359c867ae3e4d6df306b53a864b5c 18.142185819 1078919 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": 232152, 
  "vin": [ {
      "gen": {
        "height": 232134
      }
    }
  ], 
  "vout": [ {
      "amount": 18142185819, 
      "target": {
        "key": "4e601faeaa78994e3f7413f6893a0060bf9359c867ae3e4d6df306b53a864b5c"
      }
    }
  ], 
  "extra": [ 1, 65, 10, 122, 79, 66, 17, 250, 159, 209, 73, 2, 13, 81, 78, 39, 229, 120, 60, 75, 107, 79, 38, 191, 14, 65, 34, 175, 0, 12, 241, 112, 69, 2, 17, 0, 0, 0, 1, 61, 214, 165, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 233, 72, 125, 144, 105, 145, 21, 92, 102, 76, 138, 83, 86, 181, 142, 45, 23, 122, 23, 140, 254, 42, 8, 12, 222, 218, 30, 98, 59, 117, 31, 96
  ], 
  "rct_signatures": {
    "type": 0
  }
}