Transaction Details
Tx hash
9bd03f89a92d5bfcb440b8cdc890beee4afbeb4e844cfdd1b84c4df9f005a2fb
Tx prefix hash
9db919c56bd8f9085af3f00c79b53eb2c2a47b2f74a97aea1e4cc58f37bb11da
Tx public key
3dfe5cb90d48ceefdefdd51fb21528a4b4da722f821c74b2117b9cb47712c8c5
Age [y:d:h:m:s]
05:316:10:40:50
Timestamp [UCT] (epoch)
2019-01-18 05:46:37 (1547790397)
Block
93282 (1507409 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
013dfe5cb90d48ceefdefdd51fb21528a4b4da722f821c74b2117b9cb47712c8c5032100d04bd058d61332e0dde01a3cae6db2d0e8d3a9a8a3eec115a8c4bfc092ca8c01021b00000000000000000000000000090c55d500000000000000000000
Outputs
1 output(s) for total of 19.384056446 ARQ
stealth address amount amount idx
00: d34ef1022e381b3d54c1922709de8fc080bbfb16eafa782b05f7e2a02173504e 19.384056446 460185 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": 93300, 
  "vin": [ {
      "gen": {
        "height": 93282
      }
    }
  ], 
  "vout": [ {
      "amount": 19384056446, 
      "target": {
        "key": "d34ef1022e381b3d54c1922709de8fc080bbfb16eafa782b05f7e2a02173504e"
      }
    }
  ], 
  "extra": [ 1, 61, 254, 92, 185, 13, 72, 206, 239, 222, 253, 213, 31, 178, 21, 40, 164, 180, 218, 114, 47, 130, 28, 116, 178, 17, 123, 156, 180, 119, 18, 200, 197, 3, 33, 0, 208, 75, 208, 88, 214, 19, 50, 224, 221, 224, 26, 60, 174, 109, 178, 208, 232, 211, 169, 168, 163, 238, 193, 21, 168, 196, 191, 192, 146, 202, 140, 1, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 12, 85, 213, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}