Transaction Details
Tx hash
731f52ab6c5f40da98249d648804070ee4d5ca4f4a4e89efcc1c6a6d239ce5a5
Tx prefix hash
bf35204b625ab7500519a6d3e083c4b410e6e027bdd0ff0b7ff0d1f8832529f7
Tx public key
12c5f90f3077e0adc5c5110366fb10bd7f51575282aa7b8440374a2c97e2ecb0
Age [y:d:h:m:s]
05:103:20:10:31
Timestamp [UCT] (epoch)
2019-08-17 22:19:57 (1566080397)
Block
244610 (1355428 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0112c5f90f3077e0adc5c5110366fb10bd7f51575282aa7b8440374a2c97e2ecb00321000c24130b4ac8ec3e7e4623b0b455e484084404cbc9b7f1bc912a030f6c267471021b00000000000000000000000000ef76922e00000000000000000000
Outputs
1 output(s) for total of 18.034513006 ARQ
stealth address amount amount idx
00: 9f67d5081916a8270ebd852f5470f4d0acdaeaa60ec60b183102c1bce9b20976 18.034513006 1104321 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": 244628, 
  "vin": [ {
      "gen": {
        "height": 244610
      }
    }
  ], 
  "vout": [ {
      "amount": 18034513006, 
      "target": {
        "key": "9f67d5081916a8270ebd852f5470f4d0acdaeaa60ec60b183102c1bce9b20976"
      }
    }
  ], 
  "extra": [ 1, 18, 197, 249, 15, 48, 119, 224, 173, 197, 197, 17, 3, 102, 251, 16, 189, 127, 81, 87, 82, 130, 170, 123, 132, 64, 55, 74, 44, 151, 226, 236, 176, 3, 33, 0, 12, 36, 19, 11, 74, 200, 236, 62, 126, 70, 35, 176, 180, 85, 228, 132, 8, 68, 4, 203, 201, 183, 241, 188, 145, 42, 3, 15, 108, 38, 116, 113, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 239, 118, 146, 46, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}