Transaction Details
Tx hash
7d779701d746f10ba7c36a24cb70368a8e3f340dd0f1be9dc510a52af781388a
Tx prefix hash
6694feb563356c7eabe8261cab29d7911382492bd7c62f7c96491dc32446ea8f
Tx public key
6842542fd330c1de42483d55f64ae98b4c5d19280be5c3e592522463208e81de
Age [y:d:h:m:s]
05:222:10:40:14
Timestamp [UCT] (epoch)
2019-04-21 22:08:13 (1555884493)
Block
160064 (1440403 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016842542fd330c1de42483d55f64ae98b4c5d19280be5c3e592522463208e81de032100f4851df2993cad39b8a8a6e0393c8dce93946e2420f22640a7e5221e079596a7021b00000000000000000000000000d40cb4f800000000000000000000
Outputs
1 output(s) for total of 18.776423154 ARQ
stealth address amount amount idx
00: 427de2c03a55f53b4c0604db3193081e8f0a0ba9b96db9c89b7f888010eade7e 18.776423154 733266 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": 160082, 
  "vin": [ {
      "gen": {
        "height": 160064
      }
    }
  ], 
  "vout": [ {
      "amount": 18776423154, 
      "target": {
        "key": "427de2c03a55f53b4c0604db3193081e8f0a0ba9b96db9c89b7f888010eade7e"
      }
    }
  ], 
  "extra": [ 1, 104, 66, 84, 47, 211, 48, 193, 222, 66, 72, 61, 85, 246, 74, 233, 139, 76, 93, 25, 40, 11, 229, 195, 229, 146, 82, 36, 99, 32, 142, 129, 222, 3, 33, 0, 244, 133, 29, 242, 153, 60, 173, 57, 184, 168, 166, 224, 57, 60, 141, 206, 147, 148, 110, 36, 32, 242, 38, 64, 167, 229, 34, 30, 7, 149, 150, 167, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 212, 12, 180, 248, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}