Transaction Details
Tx hash
1d603cb2f886e670df6df37055a9c46e3dcf769dc8a6d63d1d3003dd94c11aa1
Tx prefix hash
ffff053cd735b7069396f8c2ac23f290c171396f86864b4dc7ec5d74acd2b8c8
Tx public key
49c7b0fbbf66d2d21edfd7eea6cc7ff30d7e9b5b661c38efe5dcff83e38ee9d9
Age [y:d:h:m:s]
05:123:01:06:57
Timestamp [UCT] (epoch)
2019-07-03 01:17:31 (1562116651)
Block
211603 (1369656 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0149c7b0fbbf66d2d21edfd7eea6cc7ff30d7e9b5b661c38efe5dcff83e38ee9d90211000000087b6771dc000000000000000000032100389affd78ae8b64f4ef1d357a6d52b57e677d02381e8c8e523aed2bc2adcbc5b
Outputs
1 output(s) for total of 18.320727711 ARQ
stealth address amount amount idx
00: 5cff94769c645839bd00127061c6306700a425bbfe8bd91a76dd130a0c610aa5 18.320727711 976216 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": 211621, 
  "vin": [ {
      "gen": {
        "height": 211603
      }
    }
  ], 
  "vout": [ {
      "amount": 18320727711, 
      "target": {
        "key": "5cff94769c645839bd00127061c6306700a425bbfe8bd91a76dd130a0c610aa5"
      }
    }
  ], 
  "extra": [ 1, 73, 199, 176, 251, 191, 102, 210, 210, 30, 223, 215, 238, 166, 204, 127, 243, 13, 126, 155, 91, 102, 28, 56, 239, 229, 220, 255, 131, 227, 142, 233, 217, 2, 17, 0, 0, 0, 8, 123, 103, 113, 220, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 56, 154, 255, 215, 138, 232, 182, 79, 78, 241, 211, 87, 166, 213, 43, 87, 230, 119, 208, 35, 129, 232, 200, 229, 35, 174, 210, 188, 42, 220, 188, 91
  ], 
  "rct_signatures": {
    "type": 0
  }
}