Transaction Details
Tx hash
fc3d29eef4743b6be3cc70ee021e9b0fd6469b04cd7f01c559b16917ad15cb94
Tx prefix hash
1ee7837a6c9185fa406cccd8a0b163b77e22d46ecc20047b53623d1dbc124703
Tx public key
d553298a5505e5ed7de5aaa5566059702b05e2c6694d91cc4fcf18782b2c3be8
Age [y:d:h:m:s]
05:255:13:59:37
Timestamp [UCT] (epoch)
2019-03-17 23:36:51 (1552865811)
Block
135225 (1463967 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01d553298a5505e5ed7de5aaa5566059702b05e2c6694d91cc4fcf18782b2c3be8032100f37d071b820342240cdaa06b4e7481617650b40d73e90db616fdddd7c9ab4d61021b00000000000000000000000000047bcc6800000000000000000000
Outputs
1 output(s) for total of 19.000136365 ARQ
stealth address amount amount idx
00: 4b4d9b3a1820136854363a33b42d70133dccb3b7386b582aefbc01bd8b4545c0 19.000136365 634361 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": 135243, 
  "vin": [ {
      "gen": {
        "height": 135225
      }
    }
  ], 
  "vout": [ {
      "amount": 19000136365, 
      "target": {
        "key": "4b4d9b3a1820136854363a33b42d70133dccb3b7386b582aefbc01bd8b4545c0"
      }
    }
  ], 
  "extra": [ 1, 213, 83, 41, 138, 85, 5, 229, 237, 125, 229, 170, 165, 86, 96, 89, 112, 43, 5, 226, 198, 105, 77, 145, 204, 79, 207, 24, 120, 43, 44, 59, 232, 3, 33, 0, 243, 125, 7, 27, 130, 3, 66, 36, 12, 218, 160, 107, 78, 116, 129, 97, 118, 80, 180, 13, 115, 233, 13, 182, 22, 253, 221, 215, 201, 171, 77, 97, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 123, 204, 104, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}