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: 72a72043fdf3f6c776d8a391475ae9f5adf084cec9916d98deed216e093e506e
Tx prefix hash: 542d835d6feb64f8866c05b3d7bd7e87bebab487cab92e9f665e8b2c425d4488
Tx public key: 39bd44c03b95fbdcd7f6a5800ca55ad0ad8830af126753f459e6099971d3fc91
| Timestamp: 1779718756 | Timestamp [UTC]: 2026-05-25 14:19:16 | Age [y:d:h:m:s]: 00:014:14:13:46 |
| Block: 1710 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6319 | RingCT/type: yes/0 |
| Extra: 0139bd44c03b95fbdcd7f6a5800ca55ad0ad8830af126753f459e6099971d3fc91020900000004ba6d17be00 | ||
1 output(s) for total of 35.069869651996 HMNY
| stealth address | amount | amount idx | tag |
| 00: a0ac91b819d9c5b71ac999f686566cc8cfda760df08387a527ca0c719bb19320 | 35.069869651996 | 1881 of 0 | <2f> |
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": 1770,
"vin": [ {
"gen": {
"height": 1710
}
}
],
"vout": [ {
"amount": 35069869651996,
"target": {
"tagged_key": {
"key": "a0ac91b819d9c5b71ac999f686566cc8cfda760df08387a527ca0c719bb19320",
"view_tag": "2f"
}
}
}
],
"extra": [ 1, 57, 189, 68, 192, 59, 149, 251, 220, 215, 246, 165, 128, 12, 165, 90, 208, 173, 136, 48, 175, 18, 103, 83, 244, 89, 230, 9, 153, 113, 211, 252, 145, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}