Transaction Details
Tx hash
e311d0b606346d368e95550af38526fa51ced3ac43653991c942af20476d4b7e
Tx prefix hash
6ed520d6bd7c6504d06dd866cdf52223088e993a52d1a969dcfbad1dfdf11b14
Tx public key
02626d3215289ee987cb23a2990f9794623df8ffa9abf149c8fec6b57c45b38d
Age [y:d:h:m:s]
05:110:05:47:01
Timestamp [UCT] (epoch)
2019-08-12 19:34:27 (1565638467)
Block
240914 (1360034 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0102626d3215289ee987cb23a2990f9794623df8ffa9abf149c8fec6b57c45b38d032100f81988f87e5f104a175e4bfd4ff48882a44f7029c2917ebf3c928d66396a22fd021b00000000000000000000000005a71522be00000000000000000000
Outputs
1 output(s) for total of 18.066324885 ARQ
stealth address amount amount idx
00: 9bf7db020814c1b8f5126994488c5dd100570da3e2322ae2066210d0bebf4e5b 18.066324885 1097862 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": 240932, 
  "vin": [ {
      "gen": {
        "height": 240914
      }
    }
  ], 
  "vout": [ {
      "amount": 18066324885, 
      "target": {
        "key": "9bf7db020814c1b8f5126994488c5dd100570da3e2322ae2066210d0bebf4e5b"
      }
    }
  ], 
  "extra": [ 1, 2, 98, 109, 50, 21, 40, 158, 233, 135, 203, 35, 162, 153, 15, 151, 148, 98, 61, 248, 255, 169, 171, 241, 73, 200, 254, 198, 181, 124, 69, 179, 141, 3, 33, 0, 248, 25, 136, 248, 126, 95, 16, 74, 23, 94, 75, 253, 79, 244, 136, 130, 164, 79, 112, 41, 194, 145, 126, 191, 60, 146, 141, 102, 57, 106, 34, 253, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 167, 21, 34, 190, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}