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: 3033d3f2f244dec2a0b20c704c76f9e8fc25be48000e03428cc23510dc620f01
Tx prefix hash: dc95e3c06136b6fdda94f1540c6471854c93bc8ca7a16d0c4b08047e8cd8ff91
Tx public key: a9238bc81ee49c1cd1c25da34813a2578ed92b4367ed9d72be9e4dc1731b5981
| Timestamp: 1779437645 | Timestamp [UTC]: 2026-05-22 08:14:05 | Age [y:d:h:m:s]: 00:017:16:32:42 |
| Block: 169 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7717 | RingCT/type: yes/0 |
| Extra: 01a9238bc81ee49c1cd1c25da34813a2578ed92b4367ed9d72be9e4dc1731b5981020900000001a662ed0300 | ||
1 output(s) for total of 35.173099595188 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0d1bfffdbd75070bdcd60a6fb183707e73966927b76194889dcfe2965ee490c7 | 35.173099595188 | 165 of 0 | <e0> |
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": 229,
"vin": [ {
"gen": {
"height": 169
}
}
],
"vout": [ {
"amount": 35173099595188,
"target": {
"tagged_key": {
"key": "0d1bfffdbd75070bdcd60a6fb183707e73966927b76194889dcfe2965ee490c7",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 169, 35, 139, 200, 30, 228, 156, 28, 209, 194, 93, 163, 72, 19, 162, 87, 142, 217, 43, 67, 103, 237, 157, 114, 190, 158, 77, 193, 115, 27, 89, 129, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}