Transaction Details
Tx hash
92df651e8ebd7f62bf7d5c435e9d53d65c44d44f603f2dd221c1ed4a0fd80a5e
Tx prefix hash
bc66f93196996a65dc0ea75b1e906084863a41cbb567fc16c99e2aa37070f150
Tx public key
8685d60a8b9b1b52c00d1eebb49c0c499f061dc60a5f63a79d0c454629d4b061
Age [y:d:h:m:s]
05:126:20:27:09
Timestamp [UCT] (epoch)
2019-07-29 09:36:18 (1564392978)
Block
230608 (1371850 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018685d60a8b9b1b52c00d1eebb49c0c499f061dc60a5f63a79d0c454629d4b061032100c937add94a4e8714c8ecd6b1e141778d041013080bbac7108f687f8bdc752400021b0000000000000000000000000b8e7975fa00000000000000000000
Outputs
1 output(s) for total of 18.155326464 ARQ
stealth address amount amount idx
00: 7a2d133aa10f40406d13da970fdc4b5382a9a58c1e49e3c05a68dd19e5a2b2a9 18.155326464 1074418 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": 230626, 
  "vin": [ {
      "gen": {
        "height": 230608
      }
    }
  ], 
  "vout": [ {
      "amount": 18155326464, 
      "target": {
        "key": "7a2d133aa10f40406d13da970fdc4b5382a9a58c1e49e3c05a68dd19e5a2b2a9"
      }
    }
  ], 
  "extra": [ 1, 134, 133, 214, 10, 139, 155, 27, 82, 192, 13, 30, 235, 180, 156, 12, 73, 159, 6, 29, 198, 10, 95, 99, 167, 157, 12, 69, 70, 41, 212, 176, 97, 3, 33, 0, 201, 55, 173, 217, 74, 78, 135, 20, 200, 236, 214, 177, 225, 65, 119, 141, 4, 16, 19, 8, 11, 186, 199, 16, 143, 104, 127, 139, 220, 117, 36, 0, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 142, 121, 117, 250, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}