Transaction Details
Tx hash
9cb3fe5320b4a8943c4bf6585af706843ae54fd03060f949999b8bdbfd495002
Tx prefix hash
d4a48c900406095f22813aafa79ec0634de0d00bde8b4816ea0a6e99170fed00
Tx public key
bf4f684dc4e278868a662597d78d622ff8fccf8173b295e107e6d2e9eabc19f1
Age [y:d:h:m:s]
05:307:17:30:20
Timestamp [UCT] (epoch)
2019-01-24 02:24:07 (1548296647)
Block
97473 (1501203 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01bf4f684dc4e278868a662597d78d622ff8fccf8173b295e107e6d2e9eabc19f103210061cfe8d3e00222b37f3994339c1cbfb360a3968ef92936e17afea92bb5f60983021b000000000000000000000000001d6f93d700000000000000000000
Outputs
1 output(s) for total of 19.345264610 ARQ
stealth address amount amount idx
00: f395a4e8c1a82931d6cc50c60d856ec7b040d79e948a680f46218833428142f4 19.345264610 480838 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": 97491, 
  "vin": [ {
      "gen": {
        "height": 97473
      }
    }
  ], 
  "vout": [ {
      "amount": 19345264610, 
      "target": {
        "key": "f395a4e8c1a82931d6cc50c60d856ec7b040d79e948a680f46218833428142f4"
      }
    }
  ], 
  "extra": [ 1, 191, 79, 104, 77, 196, 226, 120, 134, 138, 102, 37, 151, 215, 141, 98, 47, 248, 252, 207, 129, 115, 178, 149, 225, 7, 230, 210, 233, 234, 188, 25, 241, 3, 33, 0, 97, 207, 232, 211, 224, 2, 34, 179, 127, 57, 148, 51, 156, 28, 191, 179, 96, 163, 150, 142, 249, 41, 54, 225, 122, 254, 169, 43, 181, 246, 9, 131, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 29, 111, 147, 215, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}