Transaction Details
Tx hash
28a6046b278530b5dbb68a05cf72c25d7204013a7ca531c7a9801f557ae4b8f8
Tx prefix hash
90efc53ded62a36419b620f88dafb4db17237e3156e13c5189eb2ba055fa9066
Tx public key
2ce2e8e6a65cfa4a9d038a4f5e6ea8c1410f3b8468f273a9e76f9b2d46887429
Age [y:d:h:m:s]
05:268:12:47:23
Timestamp [UCT] (epoch)
2019-03-07 01:43:05 (1551922985)
Block
127475 (1473168 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
012ce2e8e6a65cfa4a9d038a4f5e6ea8c1410f3b8468f273a9e76f9b2d4688742903210084078c7c4cadb3c77fc4e6abbbb2c1ec3399993f2647a2c25f5cd30c70d09498021b00000000000000000000000000de5cd6ec00000000000000000000
Outputs
1 output(s) for total of 19.070481022 ARQ
stealth address amount amount idx
00: a5e4347cf4e9bfcf50446e7d19ec54f3d5d1a97113f0cfe466693c0835b07a7c 19.070481022 608806 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": 127493, 
  "vin": [ {
      "gen": {
        "height": 127475
      }
    }
  ], 
  "vout": [ {
      "amount": 19070481022, 
      "target": {
        "key": "a5e4347cf4e9bfcf50446e7d19ec54f3d5d1a97113f0cfe466693c0835b07a7c"
      }
    }
  ], 
  "extra": [ 1, 44, 226, 232, 230, 166, 92, 250, 74, 157, 3, 138, 79, 94, 110, 168, 193, 65, 15, 59, 132, 104, 242, 115, 169, 231, 111, 155, 45, 70, 136, 116, 41, 3, 33, 0, 132, 7, 140, 124, 76, 173, 179, 199, 127, 196, 230, 171, 187, 178, 193, 236, 51, 153, 153, 63, 38, 71, 162, 194, 95, 92, 211, 12, 112, 208, 148, 152, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 222, 92, 214, 236, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}