Transaction Details
Tx hash
3ca2cd992a64b48a659e297fb02fd33765c3c0578f0d4ea35140a2f2d3fa39e4
Tx prefix hash
e1046b1d5cf0849cec8fad455fc08008c083bb719b2941dad6abcdf3810e9e0f
Tx public key
7d6b06fe3fb31e8d43a9cf6c7fcf46a6af4d1f3d3e70f84cda8b354590b3c5ac
Age [y:d:h:m:s]
05:175:01:57:06
Timestamp [UCT] (epoch)
2019-04-15 11:18:23 (1555327103)
Block
155417 (1407071 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
017d6b06fe3fb31e8d43a9cf6c7fcf46a6af4d1f3d3e70f84cda8b354590b3c5ac032100a97d101529c9655d593abca268544f8afb9e3bb19caab33819bc2dfeddcd235d021b000000000000000000000000000311a68800000000000000000000
Outputs
1 output(s) for total of 18.818075262 ARQ
stealth address amount amount idx
00: a8124762d05a442fc3f8648e7f75c7772648528f7df4bc640f4bb44dd650c7d1 18.818075262 711736 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": 155435, 
  "vin": [ {
      "gen": {
        "height": 155417
      }
    }
  ], 
  "vout": [ {
      "amount": 18818075262, 
      "target": {
        "key": "a8124762d05a442fc3f8648e7f75c7772648528f7df4bc640f4bb44dd650c7d1"
      }
    }
  ], 
  "extra": [ 1, 125, 107, 6, 254, 63, 179, 30, 141, 67, 169, 207, 108, 127, 207, 70, 166, 175, 77, 31, 61, 62, 112, 248, 76, 218, 139, 53, 69, 144, 179, 197, 172, 3, 33, 0, 169, 125, 16, 21, 41, 201, 101, 93, 89, 58, 188, 162, 104, 84, 79, 138, 251, 158, 59, 177, 156, 170, 179, 56, 25, 188, 45, 254, 221, 205, 35, 93, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 17, 166, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}