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: b5ad9fe7cc9df681b2dba711de08d74942d1db6007ef48464acff7eb8342fd5c
Tx prefix hash: ae397c0c1d990e443eb60b3a809d272b86dc34766fd1bfdb4f575b598ae42766
Tx public key: ed658721b037ae4e1d21eb76af5647d923dcf32fc8a4ee0978ec61178d862fa3
| Timestamp: 1779942657 | Timestamp [UTC]: 2026-05-28 04:30:57 | Age [y:d:h:m:s]: 00:011:18:47:56 |
| Block: 3522 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4364 | RingCT/type: yes/0 |
| Extra: 01ed658721b037ae4e1d21eb76af5647d923dcf32fc8a4ee0978ec61178d862fa302090000000126697be300 | ||
1 output(s) for total of 34.948873217987 HMNY
| stealth address | amount | amount idx | tag |
| 00: 54d744e73d57e854d866d57c7452d59fefce21aeacb557dcbc1cc21ddd146277 | 34.948873217987 | 4248 of 0 | <de> |
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": 3582,
"vin": [ {
"gen": {
"height": 3522
}
}
],
"vout": [ {
"amount": 34948873217987,
"target": {
"tagged_key": {
"key": "54d744e73d57e854d866d57c7452d59fefce21aeacb557dcbc1cc21ddd146277",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 237, 101, 135, 33, 176, 55, 174, 78, 29, 33, 235, 118, 175, 86, 71, 217, 35, 220, 243, 47, 200, 164, 238, 9, 120, 236, 97, 23, 141, 134, 47, 163, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}