Transaction Details
Tx hash
4071a0ce3566cdf18aba41b85b7c614a459dff23d98def626b93f5938141081e
Tx prefix hash
56912ffa3eec8b1a4f06e3908483731c9520902fd519312df64029af8b25ce8f
Tx public key
f0d512e657ff6904888d49fd911104b07ba6cd04f8093bca11cffe5a81afff5b
Age [y:d:h:m:s]
05:267:20:46:16
Timestamp [UCT] (epoch)
2019-01-12 07:17:12 (1547277432)
Block
89028 (1473178 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01f0d512e657ff6904888d49fd911104b07ba6cd04f8093bca11cffe5a81afff5b032100f3517ccd0924f900002a312a8bb1a6802e0acde16ce97b46c050f84486eda715021b000000000000000000000000000736d44000000000000000000000
Outputs
1 output(s) for total of 19.423369558 ARQ
stealth address amount amount idx
00: 7c4d8b5a8c27583a39f7055f2adb03f245bd80f8d763d9f7c51dae743d8217e6 19.423369558 440336 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": 89046, 
  "vin": [ {
      "gen": {
        "height": 89028
      }
    }
  ], 
  "vout": [ {
      "amount": 19423369558, 
      "target": {
        "key": "7c4d8b5a8c27583a39f7055f2adb03f245bd80f8d763d9f7c51dae743d8217e6"
      }
    }
  ], 
  "extra": [ 1, 240, 213, 18, 230, 87, 255, 105, 4, 136, 141, 73, 253, 145, 17, 4, 176, 123, 166, 205, 4, 248, 9, 59, 202, 17, 207, 254, 90, 129, 175, 255, 91, 3, 33, 0, 243, 81, 124, 205, 9, 36, 249, 0, 0, 42, 49, 42, 139, 177, 166, 128, 46, 10, 205, 225, 108, 233, 123, 70, 192, 80, 248, 68, 134, 237, 167, 21, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 54, 212, 64, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}