Transaction Details
Tx hash
23372e6bfa5dacbc6a429d6ad68c777af0487c6dd84b8fe02f393404e3c0efec
Tx prefix hash
e4fdef334049dfb4175830dca624d2de57b595e8783bc0887f7f182a8b86d627
Tx public key
20f1154415a0f5d4d3bdafc0c1f8bdb74fe9c430dd3ae8a37e5af04c27433d30
Age [y:d:h:m:s]
05:052:07:39:44
Timestamp [UCT] (epoch)
2019-10-09 09:56:28 (1570614988)
Block
281724 (1318997 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0120f1154415a0f5d4d3bdafc0c1f8bdb74fe9c430dd3ae8a37e5af04c27433d30021100000012b8f7d4e5000000020000050a00032100127a1331d9dabf9e4f6f4fd0685d14a82ec59c3c740ee8e542bd12caf3ac383e
Outputs
1 output(s) for total of 20.111472805 ARQ
stealth address amount amount idx
00: d50cc40f5f7064d4084a417f83fe29a600b5331a3e368cf9afc4c826d2d8fb5b 20.111472805 1269187 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": 281742, 
  "vin": [ {
      "gen": {
        "height": 281724
      }
    }
  ], 
  "vout": [ {
      "amount": 20111472805, 
      "target": {
        "key": "d50cc40f5f7064d4084a417f83fe29a600b5331a3e368cf9afc4c826d2d8fb5b"
      }
    }
  ], 
  "extra": [ 1, 32, 241, 21, 68, 21, 160, 245, 212, 211, 189, 175, 192, 193, 248, 189, 183, 79, 233, 196, 48, 221, 58, 232, 163, 126, 90, 240, 76, 39, 67, 61, 48, 2, 17, 0, 0, 0, 18, 184, 247, 212, 229, 0, 0, 0, 2, 0, 0, 5, 10, 0, 3, 33, 0, 18, 122, 19, 49, 217, 218, 191, 158, 79, 111, 79, 208, 104, 93, 20, 168, 46, 197, 156, 60, 116, 14, 232, 229, 66, 189, 18, 202, 243, 172, 56, 62
  ], 
  "rct_signatures": {
    "type": 0
  }
}