Transaction Details
Tx hash
dbc1b7de9cb7cf090e0cf98c88b4e53abf3806e773450d2ffceeb81c526b4809
Tx prefix hash
486c5f8bf01d0541372f4bd84bea7c209ebd01fec5886b545bf0384dd05c8c80
Tx public key
da0d12dd752b2229958669e833394dac4b392f2d887d6082e0063addeb774330
Age [y:d:h:m:s]
05:276:06:26:29
Timestamp [UCT] (epoch)
2019-02-27 14:00:58 (1551276058)
Block
122086 (1478713 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01da0d12dd752b2229958669e833394dac4b392f2d887d6082e0063addeb77433003210076c76eb82cd4f04f4ae7d8ac6ceae57937f9beb5a697af9451b3e75751903d83021b0000000000000000000000000140b34b1000000000000000000000
Outputs
1 output(s) for total of 19.119854811 ARQ
stealth address amount amount idx
00: b2bb2a969e913fecea8140b31209ea29eee52f3d8c8561e40e7ead76a14004e1 19.119854811 588108 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": 122104, 
  "vin": [ {
      "gen": {
        "height": 122086
      }
    }
  ], 
  "vout": [ {
      "amount": 19119854811, 
      "target": {
        "key": "b2bb2a969e913fecea8140b31209ea29eee52f3d8c8561e40e7ead76a14004e1"
      }
    }
  ], 
  "extra": [ 1, 218, 13, 18, 221, 117, 43, 34, 41, 149, 134, 105, 232, 51, 57, 77, 172, 75, 57, 47, 45, 136, 125, 96, 130, 224, 6, 58, 221, 235, 119, 67, 48, 3, 33, 0, 118, 199, 110, 184, 44, 212, 240, 79, 74, 231, 216, 172, 108, 234, 229, 121, 55, 249, 190, 181, 166, 151, 175, 148, 81, 179, 231, 87, 81, 144, 61, 131, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 64, 179, 75, 16, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}