Transaction Details
Tx hash
decfb62a93058a2de76758e60d03b06a7204ef27bb561d8ded949582958dba52
Tx prefix hash
949bd58e3bdb123ab37ecd8d07e394473e39be841db79d9cad7421af169743c7
Tx public key
7a1979f84f482ee943dff66a1c8257809aa8b51ca05e1287d9a79db73f367fc0
Age [y:d:h:m:s]
05:310:05:58:07
Timestamp [UCT] (epoch)
2019-01-24 18:29:21 (1548354561)
Block
97912 (1503006 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
017a1979f84f482ee943dff66a1c8257809aa8b51ca05e1287d9a79db73f367fc0032100f49469b3e3ccc48a17ebeecc47d5b52f5efe555d1cf26fd891fa320ee51a2543021b000000000000000000000000000e6f93d700000000000000000000
Outputs
1 output(s) for total of 19.341215460 ARQ
stealth address amount amount idx
00: 324b33eb6264166ef3fbb60274ee0b18323b8f783883b25fb08987cb3f504f47 19.341215460 483346 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": 97930, 
  "vin": [ {
      "gen": {
        "height": 97912
      }
    }
  ], 
  "vout": [ {
      "amount": 19341215460, 
      "target": {
        "key": "324b33eb6264166ef3fbb60274ee0b18323b8f783883b25fb08987cb3f504f47"
      }
    }
  ], 
  "extra": [ 1, 122, 25, 121, 248, 79, 72, 46, 233, 67, 223, 246, 106, 28, 130, 87, 128, 154, 168, 181, 28, 160, 94, 18, 135, 217, 167, 157, 183, 63, 54, 127, 192, 3, 33, 0, 244, 148, 105, 179, 227, 204, 196, 138, 23, 235, 238, 204, 71, 213, 181, 47, 94, 254, 85, 93, 28, 242, 111, 216, 145, 250, 50, 14, 229, 26, 37, 67, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 14, 111, 147, 215, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}