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: 00d5b63c8e8c5af4b9e1e4ed99116c6054caaf1cd00dee349c48d61cfb5cec99
Tx prefix hash: 934d63f3311da905c2fced9a9be5c5bb33715d3ee13e8cca87b5b582d6aca638
Tx public key: 71d5e3a45204ac6814eaf23c28da3c5ff2c74ccbc045f7d2f7765d9be333ed5c
| Timestamp: 1780085453 | Timestamp [UTC]: 2026-05-29 20:10:53 | Age [y:d:h:m:s]: 00:010:07:27:57 |
| Block: 4809 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3132 | RingCT/type: yes/0 |
| Extra: 0171d5e3a45204ac6814eaf23c28da3c5ff2c74ccbc045f7d2f7765d9be333ed5c02090000000226697be300 | ||
1 output(s) for total of 34.863187333037 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff7dfc2b62875b99030b36429975bcf16bd7cf0dc1d5c18ea1cfa795d958bb17 | 34.863187333037 | 6049 of 0 | <f8> |
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": 4869,
"vin": [ {
"gen": {
"height": 4809
}
}
],
"vout": [ {
"amount": 34863187333037,
"target": {
"tagged_key": {
"key": "ff7dfc2b62875b99030b36429975bcf16bd7cf0dc1d5c18ea1cfa795d958bb17",
"view_tag": "f8"
}
}
}
],
"extra": [ 1, 113, 213, 227, 164, 82, 4, 172, 104, 20, 234, 242, 60, 40, 218, 60, 95, 242, 199, 76, 203, 192, 69, 247, 210, 247, 118, 93, 155, 227, 51, 237, 92, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}