Transaction Details
Tx hash
bd2b288eb3996330d0270624db19091748d4f420bca45f3a3625cd2015d044ee
Tx prefix hash
728909bdb8b07289b7710ca7a5844c686d041ba39f4bb8c2867d5d50914afd83
Tx public key
0df8cb6428098b906b679eaeda818a131a34795a5f192c64f0cd745e3b1976f8
Age [y:d:h:m:s]
05:323:19:07:22
Timestamp [UCT] (epoch)
2019-01-10 17:05:05 (1547139905)
Block
87900 (1512667 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010df8cb6428098b906b679eaeda818a131a34795a5f192c64f0cd745e3b1976f8032100c480db55c0067495b8dca93d995f8ca504486478e3257b6aa008735eb9efe113021b0000000000000000000000000048db7adf00000000000000000000
Outputs
1 output(s) for total of 19.433773019 ARQ
stealth address amount amount idx
00: 54adc8eb8ca58fe877b86003d2c7aa0a87a547e274ea8f3b45aec75f041d46b2 19.433773019 434126 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": 87918, 
  "vin": [ {
      "gen": {
        "height": 87900
      }
    }
  ], 
  "vout": [ {
      "amount": 19433773019, 
      "target": {
        "key": "54adc8eb8ca58fe877b86003d2c7aa0a87a547e274ea8f3b45aec75f041d46b2"
      }
    }
  ], 
  "extra": [ 1, 13, 248, 203, 100, 40, 9, 139, 144, 107, 103, 158, 174, 218, 129, 138, 19, 26, 52, 121, 90, 95, 25, 44, 100, 240, 205, 116, 94, 59, 25, 118, 248, 3, 33, 0, 196, 128, 219, 85, 192, 6, 116, 149, 184, 220, 169, 61, 153, 95, 140, 165, 4, 72, 100, 120, 227, 37, 123, 106, 160, 8, 115, 94, 185, 239, 225, 19, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 72, 219, 122, 223, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}