Transaction Details
Tx hash
cfe844001dae492dd66a750ae6aa0d0895f32fead2ee8fc0a357baba4e424967
Tx prefix hash
89065f4d9f002376385566cf866e85a427292572a1b015ca94c29f982321267e
Tx public key
d59006239af7e5e2a5105721cf8f436cb4dde8ca7311b9dac3c9f68124f9abe8
Age [y:d:h:m:s]
05:154:17:52:25
Timestamp [UCT] (epoch)
2019-06-26 16:35:02 (1561566902)
Block
207053 (1392049 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01d59006239af7e5e2a5105721cf8f436cb4dde8ca7311b9dac3c9f68124f9abe803210041eb7791340cb74cc3c23b17b19deafc64da2845385770a3563bbe4095f80fd8021b00000000000000000000000000253fd33900000000000000000000
Outputs
1 output(s) for total of 18.360394808 ARQ
stealth address amount amount idx
00: a35cb8f540644ce4589c0a841fd4a6e23e1d87331310b8b5c0c9aa7deda8e8a1 18.360394808 949229 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": 207071, 
  "vin": [ {
      "gen": {
        "height": 207053
      }
    }
  ], 
  "vout": [ {
      "amount": 18360394808, 
      "target": {
        "key": "a35cb8f540644ce4589c0a841fd4a6e23e1d87331310b8b5c0c9aa7deda8e8a1"
      }
    }
  ], 
  "extra": [ 1, 213, 144, 6, 35, 154, 247, 229, 226, 165, 16, 87, 33, 207, 143, 67, 108, 180, 221, 232, 202, 115, 17, 185, 218, 195, 201, 246, 129, 36, 249, 171, 232, 3, 33, 0, 65, 235, 119, 145, 52, 12, 183, 76, 195, 194, 59, 23, 177, 157, 234, 252, 100, 218, 40, 69, 56, 87, 112, 163, 86, 59, 190, 64, 149, 248, 15, 216, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 37, 63, 211, 57, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}