Transaction Details
Tx hash
8997684cb51793616012d29fdb04f4ada5e2c17bef287b5034ee2d3601c4ca99
Tx prefix hash
340c7bbb49032199fb338849eec4b5af3c0c29d1500e808d306a8fc2859f4971
Tx public key
f12580480224db84ae8380a4e5877e6ea1f55a016b6f008fdcff57554dcad253
Age [y:d:h:m:s]
04:353:16:15:57
Timestamp [UCT] (epoch)
2019-10-18 22:05:32 (1571436332)
Block
288456 (1274048 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01f12580480224db84ae8380a4e5877e6ea1f55a016b6f008fdcff57554dcad253032100c8f451d7539e75c18596b12b3757e8af8710020bcd9a7ea34292a5f050868b91021b000000000000000000000000002997df8f00000000000000000000
Outputs
1 output(s) for total of 20.047005984 ARQ
stealth address amount amount idx
00: 63f5550748ba42785e6f20466ffc018fd7d20468a6939a5bb8f080f78219aee2 20.047005984 1300943 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": 288474, 
  "vin": [ {
      "gen": {
        "height": 288456
      }
    }
  ], 
  "vout": [ {
      "amount": 20047005984, 
      "target": {
        "key": "63f5550748ba42785e6f20466ffc018fd7d20468a6939a5bb8f080f78219aee2"
      }
    }
  ], 
  "extra": [ 1, 241, 37, 128, 72, 2, 36, 219, 132, 174, 131, 128, 164, 229, 135, 126, 110, 161, 245, 90, 1, 107, 111, 0, 143, 220, 255, 87, 85, 77, 202, 210, 83, 3, 33, 0, 200, 244, 81, 215, 83, 158, 117, 193, 133, 150, 177, 43, 55, 87, 232, 175, 135, 16, 2, 11, 205, 154, 126, 163, 66, 146, 165, 240, 80, 134, 139, 145, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 41, 151, 223, 143, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}