Transaction Details
Tx hash
a70e71d1dc3e6e69fbb9c722c5c2aaa8172ef134f6e008f38b7cf76feeb0f47f
Tx prefix hash
954d5a1a54b47d59f6fd9e592dab2923ad701c219522ddc1b60e91e3c4f5bc51
Tx public key
8fa66c09ca8b706ed0f5b0e81a72f851e16d9a53ce377a0c83f16212215f7ad6
Age [y:d:h:m:s]
05:048:14:59:27
Timestamp [UCT] (epoch)
2019-10-13 02:04:00 (1570932240)
Block
284322 (1316385 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
018fa66c09ca8b706ed0f5b0e81a72f851e16d9a53ce377a0c83f16212215f7ad6021100000002b84b616c00000000000000000003210086f8549f710e8f0fe897872481df9b7df8bf3668ee9d32c2a77b1e0ffa5d694b
Outputs
1 output(s) for total of 20.086573265 ARQ
stealth address amount amount idx
00: 8cfc196b3b5fee02f70412fa37221a3f0f6ddf3990c31d706aa80416a182626b 20.086573265 1281044 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": 284340, 
  "vin": [ {
      "gen": {
        "height": 284322
      }
    }
  ], 
  "vout": [ {
      "amount": 20086573265, 
      "target": {
        "key": "8cfc196b3b5fee02f70412fa37221a3f0f6ddf3990c31d706aa80416a182626b"
      }
    }
  ], 
  "extra": [ 1, 143, 166, 108, 9, 202, 139, 112, 110, 208, 245, 176, 232, 26, 114, 248, 81, 225, 109, 154, 83, 206, 55, 122, 12, 131, 241, 98, 18, 33, 95, 122, 214, 2, 17, 0, 0, 0, 2, 184, 75, 97, 108, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 134, 248, 84, 159, 113, 14, 143, 15, 232, 151, 135, 36, 129, 223, 155, 125, 248, 191, 54, 104, 238, 157, 50, 194, 167, 123, 30, 15, 250, 93, 105, 75
  ], 
  "rct_signatures": {
    "type": 0
  }
}