Transaction Details
Tx hash
610d889e331a8989f6711ccf2dc3eb18c0b14a47a374c352f5accdcafac3eddf
Tx prefix hash
b7dbd55093e98c99c4fe72dc76076610630aac865bd0ad279f6046112a9418e9
Tx public key
63fc92a45a59f4b711c314acd07375c01ddeb6faa45e36afa68f91e6e49b5266
Age [y:d:h:m:s]
05:340:03:28:50
Timestamp [UCT] (epoch)
2018-12-25 18:04:37 (1545761077)
Block
76614 (1524217 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0163fc92a45a59f4b711c314acd07375c01ddeb6faa45e36afa68f91e6e49b5266032100af179dc415b0ff7c3eb4fd491033d9c85d4a07e75584e547e572587852cdb380021b0000000000000000000000000001b285ac00000000000000000000
Outputs
1 output(s) for total of 19.538639450 ARQ
stealth address amount amount idx
00: 1f41d11f85d60f127a9e4ae3db8fc5a249a131b106a082314b4293b86dd042b9 19.538639450 385311 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": 76632, 
  "vin": [ {
      "gen": {
        "height": 76614
      }
    }
  ], 
  "vout": [ {
      "amount": 19538639450, 
      "target": {
        "key": "1f41d11f85d60f127a9e4ae3db8fc5a249a131b106a082314b4293b86dd042b9"
      }
    }
  ], 
  "extra": [ 1, 99, 252, 146, 164, 90, 89, 244, 183, 17, 195, 20, 172, 208, 115, 117, 192, 29, 222, 182, 250, 164, 94, 54, 175, 166, 143, 145, 230, 228, 155, 82, 102, 3, 33, 0, 175, 23, 157, 196, 21, 176, 255, 124, 62, 180, 253, 73, 16, 51, 217, 200, 93, 74, 7, 231, 85, 132, 229, 71, 229, 114, 88, 120, 82, 205, 179, 128, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 178, 133, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}