Transaction Details
Tx hash
5ccc2e502015bf3a19ee8d9c2ec5ab6510dad004bc06dd71f618cd910c0ecd5f
Tx prefix hash
b271042576ef4638f1dd899b7970db7da4ef4984907d72d4153e08090b1b4dc4
Tx public key
edd7b3268ead50bf27b31eab6dfa76bae8da6131b0faa249737c161e19e9033e
Age [y:d:h:m:s]
05:217:17:51:13
Timestamp [UCT] (epoch)
2019-04-23 23:30:42 (1556062242)
Block
161520 (1437074 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01edd7b3268ead50bf27b31eab6dfa76bae8da6131b0faa249737c161e19e9033e032100c1ed719231ca934990bd92a7a79410e0ed84d25248cc02df998bd8e51625ce7d021b00000000000000000000000000c761708600000000000000000000
Outputs
1 output(s) for total of 18.763391676 ARQ
stealth address amount amount idx
00: 41c494e5446f64b2d0f3c41106450cbe4c79979a3afccad0d2c5fedef4624ae8 18.763391676 739361 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": 161538, 
  "vin": [ {
      "gen": {
        "height": 161520
      }
    }
  ], 
  "vout": [ {
      "amount": 18763391676, 
      "target": {
        "key": "41c494e5446f64b2d0f3c41106450cbe4c79979a3afccad0d2c5fedef4624ae8"
      }
    }
  ], 
  "extra": [ 1, 237, 215, 179, 38, 142, 173, 80, 191, 39, 179, 30, 171, 109, 250, 118, 186, 232, 218, 97, 49, 176, 250, 162, 73, 115, 124, 22, 30, 25, 233, 3, 62, 3, 33, 0, 193, 237, 113, 146, 49, 202, 147, 73, 144, 189, 146, 167, 167, 148, 16, 224, 237, 132, 210, 82, 72, 204, 2, 223, 153, 139, 216, 229, 22, 37, 206, 125, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 199, 97, 112, 134, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}