Transaction Details
Tx hash
5d8423f0f132b668bd5626c9227e352dbe526cb32bc7a08b5bdf5d31d3e117d1
Tx prefix hash
1c0b2b0c08120729a8ec9c8fd3d8c7773adc0eca6f3c8b7c80a461a1b192090d
Tx public key
a40cd60c231c70f8a3a7c46b130be26a153ad77f3298d6fbb9b8d9d5ebf6ce5a
Age [y:d:h:m:s]
05:232:23:56:26
Timestamp [UCT] (epoch)
2019-04-08 09:31:01 (1554715861)
Block
150384 (1447986 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a40cd60c231c70f8a3a7c46b130be26a153ad77f3298d6fbb9b8d9d5ebf6ce5a0321000f142387209a07ed54657f5b6322dcdbc08e35d4dce618bcf485ba3b674c0134021b000000000000000000000000000a9c3e8400000000000000000000
Outputs
1 output(s) for total of 18.863563211 ARQ
stealth address amount amount idx
00: 319643c5b89103d092e79c16933fb8a3a1e8d4dda0bef499d2135f72b01ae138 18.863563211 688435 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": 150402, 
  "vin": [ {
      "gen": {
        "height": 150384
      }
    }
  ], 
  "vout": [ {
      "amount": 18863563211, 
      "target": {
        "key": "319643c5b89103d092e79c16933fb8a3a1e8d4dda0bef499d2135f72b01ae138"
      }
    }
  ], 
  "extra": [ 1, 164, 12, 214, 12, 35, 28, 112, 248, 163, 167, 196, 107, 19, 11, 226, 106, 21, 58, 215, 127, 50, 152, 214, 251, 185, 184, 217, 213, 235, 246, 206, 90, 3, 33, 0, 15, 20, 35, 135, 32, 154, 7, 237, 84, 101, 127, 91, 99, 34, 220, 219, 192, 142, 53, 212, 220, 230, 24, 188, 244, 133, 186, 59, 103, 76, 1, 52, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 156, 62, 132, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}