Transaction Details
Tx hash
427eb71f1a772cfb458187169eb6a263425419d100c8fe3615e873a768d80631
Tx prefix hash
d72c5e7fadbf6248bf5333c1a65378add27114166280b48e1ab4154046d8515d
Tx public key
f7f58be824120c19d72875b37fcad400d267af304f38f65d14b6efc9c29d043e
Age [y:d:h:m:s]
05:323:22:37:57
Timestamp [UCT] (epoch)
2019-01-10 18:40:30 (1547145630)
Block
87946 (1512770 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01f7f58be824120c19d72875b37fcad400d267af304f38f65d14b6efc9c29d043e032100e929c9d23b6ab44c07391d9f3814531833703fa9ba65ebf96caca06e4a700fa2021b00000000000000000000000000062e494400000000000000000000
Outputs
1 output(s) for total of 19.433346753 ARQ
stealth address amount amount idx
00: 5d6dcf171975da7b21da0c4e2cc83aa5e39ef8f5ddcbd6e4b7be05d6e91949b5 19.433346753 434374 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": 87964, 
  "vin": [ {
      "gen": {
        "height": 87946
      }
    }
  ], 
  "vout": [ {
      "amount": 19433346753, 
      "target": {
        "key": "5d6dcf171975da7b21da0c4e2cc83aa5e39ef8f5ddcbd6e4b7be05d6e91949b5"
      }
    }
  ], 
  "extra": [ 1, 247, 245, 139, 232, 36, 18, 12, 25, 215, 40, 117, 179, 127, 202, 212, 0, 210, 103, 175, 48, 79, 56, 246, 93, 20, 182, 239, 201, 194, 157, 4, 62, 3, 33, 0, 233, 41, 201, 210, 59, 106, 180, 76, 7, 57, 29, 159, 56, 20, 83, 24, 51, 112, 63, 169, 186, 101, 235, 249, 108, 172, 160, 110, 74, 112, 15, 162, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 46, 73, 68, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}