Transaction Details
Tx hash
5e84744da8a1634ef1e7b5c1b0814211d9d890776f691a6108040cd627c848a3
Tx prefix hash
230035ed0ff6413baf14b8d934158ed0e9906e44426287778dee4c79e3070c7a
Tx public key
aee5b7352de7078e737a42cb3bfa297c066a071545d05112391390959491b0f7
Age [y:d:h:m:s]
05:322:13:41:57
Timestamp [UCT] (epoch)
2019-01-12 03:09:31 (1547262571)
Block
88916 (1511789 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1367 kB
Tx version
2
RingCT type
0
Extra
01aee5b7352de7078e737a42cb3bfa297c066a071545d05112391390959491b0f7032107bf7075efd40664dbc68d78c1f3d51623785ffc7ac89d21f859beb9ff41a75ca902140000000759d82e00000000000000000000000000
Outputs
1 output(s) for total of 19.424360284 ARQ
stealth address amount amount idx
00: b2fb41e8ea17b9b3ef2c744841ceac7b359f006d7bb41c945ffb891d957812f3 19.424360284 439749 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": 88934, 
  "vin": [ {
      "gen": {
        "height": 88916
      }
    }
  ], 
  "vout": [ {
      "amount": 19424360284, 
      "target": {
        "key": "b2fb41e8ea17b9b3ef2c744841ceac7b359f006d7bb41c945ffb891d957812f3"
      }
    }
  ], 
  "extra": [ 1, 174, 229, 183, 53, 45, 231, 7, 142, 115, 122, 66, 203, 59, 250, 41, 124, 6, 106, 7, 21, 69, 208, 81, 18, 57, 19, 144, 149, 148, 145, 176, 247, 3, 33, 7, 191, 112, 117, 239, 212, 6, 100, 219, 198, 141, 120, 193, 243, 213, 22, 35, 120, 95, 252, 122, 200, 157, 33, 248, 89, 190, 185, 255, 65, 167, 92, 169, 2, 20, 0, 0, 0, 7, 89, 216, 46, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}