Transaction Details
Tx hash
77715a550afdc56c6a09893acc4312c4f62d485e3961a036dd1f725b2775ef8f
Tx prefix hash
4cb8b0c29fd1cfc9ad080a17083e99a4d46bfec6f310f3e192feda8bb748de2f
Tx public key
015f7d34b00d21d6543d5b3f8c05cc8e1f57371bd19d2d3d74d15ed6e68eafa0
Age [y:d:h:m:s]
05:191:15:33:47
Timestamp [UCT] (epoch)
2019-05-22 15:02:41 (1558537361)
Block
182051 (1418351 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01015f7d34b00d21d6543d5b3f8c05cc8e1f57371bd19d2d3d74d15ed6e68eafa003210089fbbd5078c09b7bfe171becc3afe60b8453f5c8bca0c0b2150f6fc69b7ddf3a021b00000000000000000000000000ad34b8e900000000000000000000
Outputs
1 output(s) for total of 18.580840847 ARQ
stealth address amount amount idx
00: 7638ad85f0374bd2dc2b53fa8a3d77c6a0098fdb3df84bf28586c21c70015a5e 18.580840847 819461 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": 182069, 
  "vin": [ {
      "gen": {
        "height": 182051
      }
    }
  ], 
  "vout": [ {
      "amount": 18580840847, 
      "target": {
        "key": "7638ad85f0374bd2dc2b53fa8a3d77c6a0098fdb3df84bf28586c21c70015a5e"
      }
    }
  ], 
  "extra": [ 1, 1, 95, 125, 52, 176, 13, 33, 214, 84, 61, 91, 63, 140, 5, 204, 142, 31, 87, 55, 27, 209, 157, 45, 61, 116, 209, 94, 214, 230, 142, 175, 160, 3, 33, 0, 137, 251, 189, 80, 120, 192, 155, 123, 254, 23, 27, 236, 195, 175, 230, 11, 132, 83, 245, 200, 188, 160, 192, 178, 21, 15, 111, 198, 155, 125, 223, 58, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 173, 52, 184, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}