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: 4064a0b1e43413ccb3c55192df9514d84bc4d1525fda781ea8063e2150efcc77
Tx prefix hash: cae8f30ebbe601013279e0239191faf1d2cdb555f98182c5e3cc2b91a1d86bef
Tx public key: dc660947eb8b50013c6780382e91170404f132e209d1a8aa71eeb327c2393116
| Timestamp: 1780126687 | Timestamp [UTC]: 2026-05-30 07:38:07 | Age [y:d:h:m:s]: 00:018:00:58:07 |
| Block: 4916 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3829 | RingCT/type: yes/0 |
| Extra: 01dc660947eb8b50013c6780382e91170404f132e209d1a8aa71eeb327c239311602090000000a26697be300 | ||
1 output(s) for total of 34.856072953212 HMNY
| stealth address | amount | amount idx | tag |
| 00: e46bb90b7bd07bb9350d5896a4791e666b9608f37ebee085ee1cb943aebbd1d3 | 34.856072953212 | 6237 of 0 | <eb> |
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": 4976,
"vin": [ {
"gen": {
"height": 4916
}
}
],
"vout": [ {
"amount": 34856072953212,
"target": {
"tagged_key": {
"key": "e46bb90b7bd07bb9350d5896a4791e666b9608f37ebee085ee1cb943aebbd1d3",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 220, 102, 9, 71, 235, 139, 80, 1, 60, 103, 128, 56, 46, 145, 23, 4, 4, 241, 50, 226, 9, 209, 168, 170, 113, 238, 179, 39, 194, 57, 49, 22, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}