Transaction Details
Tx hash
db4e5244010688b8361190168d10b18b59d7f9969a2b9bea8ddb77043b09dcfa
Tx prefix hash
ab186de97d6076bea5227bb04567e0b0256fe1ff3914cf1fc5377f9d73053fc0
Tx public key
2a07473c202664f49ae5cbdb2ecc51d98f6002fe62e8cfe52d56d3fc98324bcc
Age [y:d:h:m:s]
05:131:21:30:03
Timestamp [UCT] (epoch)
2019-07-22 06:07:03 (1563775623)
Block
225388 (1375624 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
012a07473c202664f49ae5cbdb2ecc51d98f6002fe62e8cfe52d56d3fc98324bcc021100000093f20f8dbf000000000000000000032100a787e9bcb02b14d59aa33719fc5e7d2cfd33b6997562805ae066947d9b08b7e5
Outputs
1 output(s) for total of 18.200573004 ARQ
stealth address amount amount idx
00: ac0d02c8f3704f24312674870ca332e4e939df142e81ec94f24207c501d7e20e 18.200573004 1054940 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": 225406, 
  "vin": [ {
      "gen": {
        "height": 225388
      }
    }
  ], 
  "vout": [ {
      "amount": 18200573004, 
      "target": {
        "key": "ac0d02c8f3704f24312674870ca332e4e939df142e81ec94f24207c501d7e20e"
      }
    }
  ], 
  "extra": [ 1, 42, 7, 71, 60, 32, 38, 100, 244, 154, 229, 203, 219, 46, 204, 81, 217, 143, 96, 2, 254, 98, 232, 207, 229, 45, 86, 211, 252, 152, 50, 75, 204, 2, 17, 0, 0, 0, 147, 242, 15, 141, 191, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 167, 135, 233, 188, 176, 43, 20, 213, 154, 163, 55, 25, 252, 94, 125, 44, 253, 51, 182, 153, 117, 98, 128, 90, 224, 102, 148, 125, 155, 8, 183, 229
  ], 
  "rct_signatures": {
    "type": 0
  }
}