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: a92c1b625ec6173d815533fce7b703e6b34d2c25cd923b445f3e4a8a4ee38022
Tx prefix hash: 793886df785dc4104f7e6be8aca0b3ab029d3fe18586fa4fb0758539b81ac58c
Tx public key: a337af86b0ab10b83dfb3d278b55d515f8833b62adddbec990a3d47612fd1a40
| Timestamp: 1780686586 | Timestamp [UTC]: 2026-06-05 19:09:46 | Age [y:d:h:m:s]: 00:011:13:26:28 |
| Block: 5435 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3310 | RingCT/type: yes/0 |
| Extra: 01a337af86b0ab10b83dfb3d278b55d515f8833b62adddbec990a3d47612fd1a40020900000001e49593ff00 | ||
1 output(s) for total of 34.821585480429 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5968dfa485aa66aedf734d9c65451cd2f4f8ca85c95e5a28a8512f7fd4cc47b5 | 34.821585480429 | 6874 of 0 | <77> |
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": 5495,
"vin": [ {
"gen": {
"height": 5435
}
}
],
"vout": [ {
"amount": 34821585480429,
"target": {
"tagged_key": {
"key": "5968dfa485aa66aedf734d9c65451cd2f4f8ca85c95e5a28a8512f7fd4cc47b5",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 163, 55, 175, 134, 176, 171, 16, 184, 61, 251, 61, 39, 139, 85, 213, 21, 248, 131, 59, 98, 173, 221, 190, 201, 144, 163, 212, 118, 18, 253, 26, 64, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}