Transaction Details
Tx hash
13813d4d5304f425ee90ca11e64c6f6f33e742b6a5e5cf3b99e302a1636b81f9
Tx prefix hash
2b5474346213650265b00e9b27f6e2be2f383bb26872e7b1f9e5db96d5f492a6
Tx public key
1fc9016ae970b08d58394e1d227e4a21bd9b5ea501b6eea5a11e990baa6bbcbd
Age [y:d:h:m:s]
05:348:20:49:48
Timestamp [UCT] (epoch)
2018-12-12 04:37:40 (1544589460)
Block
66933 (1530474 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
011fc9016ae970b08d58394e1d227e4a21bd9b5ea501b6eea5a11e990baa6bbcbd0321006bf4159c06d674f1a925d1dd0f9f76a8ec51dbb78c5bbc696f83d8c6f5d54f37021000000019fc1c01000000000000000000
Outputs
1 output(s) for total of 19.629043425 ARQ
stealth address amount amount idx
00: 7f4b021f00a93f5e95e7aa772534ec84c7e686fedb33a9d0fa404bed2cb955e4 19.629043425 353121 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": 66951, 
  "vin": [ {
      "gen": {
        "height": 66933
      }
    }
  ], 
  "vout": [ {
      "amount": 19629043425, 
      "target": {
        "key": "7f4b021f00a93f5e95e7aa772534ec84c7e686fedb33a9d0fa404bed2cb955e4"
      }
    }
  ], 
  "extra": [ 1, 31, 201, 1, 106, 233, 112, 176, 141, 88, 57, 78, 29, 34, 126, 74, 33, 189, 155, 94, 165, 1, 182, 238, 165, 161, 30, 153, 11, 170, 107, 188, 189, 3, 33, 0, 107, 244, 21, 156, 6, 214, 116, 241, 169, 37, 209, 221, 15, 159, 118, 168, 236, 81, 219, 183, 140, 91, 188, 105, 111, 131, 216, 198, 245, 213, 79, 55, 2, 16, 0, 0, 0, 25, 252, 28, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}