For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 37511e5893b89407606e9c0467a1f58e8b38de79b4013670072bebbed5a60db6
Tx prefix hash: 6921c03f0eccb2f70cd5a2bd65dfc17a66423fd1c3cf5f9c6c1b35751bac9dc9
Tx public key: ceaed10edf01b8fdd758ebbf227dd40157e1ca29cde01dc9c4176eff3183aaed
| Timestamp: 1780083081 | Timestamp [UTC]: 2026-05-29 19:31:21 | Age [y:d:h:m:s]: 00:010:02:53:28 |
| Block: 4784 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3102 | RingCT/type: yes/0 |
| Extra: 01ceaed10edf01b8fdd758ebbf227dd40157e1ca29cde01dc9c4176eff3183aaed02090000000126697be300 | ||
1 output(s) for total of 34.864849780575 HMNY
| stealth address | amount | amount idx | tag |
| 00: 954e39fdf20c8d78dcbd33d890deefbd211cdd8182d3a7346196fb4cf5c961a5 | 34.864849780575 | 6015 of 0 | <53> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
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": 4844,
"vin": [ {
"gen": {
"height": 4784
}
}
],
"vout": [ {
"amount": 34864849780575,
"target": {
"tagged_key": {
"key": "954e39fdf20c8d78dcbd33d890deefbd211cdd8182d3a7346196fb4cf5c961a5",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 206, 174, 209, 14, 223, 1, 184, 253, 215, 88, 235, 191, 34, 125, 212, 1, 87, 225, 202, 41, 205, 224, 29, 201, 196, 23, 110, 255, 49, 131, 170, 237, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}