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: 2186c347d65508f7753d248ef23c7ef4af5753a2b39729b090390094931173ac
Tx prefix hash: 1aefd9ec79f48d2737ce6265b815073c0bd0ecb1f911190866676deb799294b8
Tx public key: 92dc5d1ffb6ff3c00d999c948e3eff26ba250c3c5b43bcfaf0ca03ed8b6679df
| Timestamp: 1779470428 | Timestamp [UTC]: 2026-05-22 17:20:28 | Age [y:d:h:m:s]: 00:017:10:30:30 |
| Block: 553 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7399 | RingCT/type: yes/0 |
| Extra: 0192dc5d1ffb6ff3c00d999c948e3eff26ba250c3c5b43bcfaf0ca03ed8b6679df02090000000393369e7d00 | ||
1 output(s) for total of 35.147347454940 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e3f5381eff5492462233a489ccc5015d9020dbc4883d33b811e87554a7d1574 | 35.147347454940 | 559 of 0 | <d3> |
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": 613,
"vin": [ {
"gen": {
"height": 553
}
}
],
"vout": [ {
"amount": 35147347454940,
"target": {
"tagged_key": {
"key": "4e3f5381eff5492462233a489ccc5015d9020dbc4883d33b811e87554a7d1574",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 146, 220, 93, 31, 251, 111, 243, 192, 13, 153, 156, 148, 142, 62, 255, 38, 186, 37, 12, 60, 91, 67, 188, 250, 240, 202, 3, 237, 139, 102, 121, 223, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}