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: 8d4f603869b38d755fefefd4e9577d848b921c8e59ac35bf05334b8691cb104b
Tx prefix hash: 0ff805536ac43b987a5a314d0ca84c02bc7e7943c03813c1abbd72bfa33841aa
Tx public key: f3928816ad56dd0dc546a6d7a716c8b92012eb4860a3f9319d915e4e0194d1b4
| Timestamp: 1780818410 | Timestamp [UTC]: 2026-06-07 07:46:50 | Age [y:d:h:m:s]: 00:006:03:15:26 |
| Block: 7111 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1634 | RingCT/type: yes/0 |
| Extra: 01f3928816ad56dd0dc546a6d7a716c8b92012eb4860a3f9319d915e4e0194d1b4020900000001e49593ff00 | ||
1 output(s) for total of 34.710448375784 HMNY
| stealth address | amount | amount idx | tag |
| 00: 82b7d46478e05e1ad3f6ea47e4f07a7189f7067e389ce85d4e02c2c654faeefa | 34.710448375784 | 8765 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": 7171,
"vin": [ {
"gen": {
"height": 7111
}
}
],
"vout": [ {
"amount": 34710448375784,
"target": {
"tagged_key": {
"key": "82b7d46478e05e1ad3f6ea47e4f07a7189f7067e389ce85d4e02c2c654faeefa",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 243, 146, 136, 22, 173, 86, 221, 13, 197, 70, 166, 215, 167, 22, 200, 185, 32, 18, 235, 72, 96, 163, 249, 49, 157, 145, 94, 78, 1, 148, 209, 180, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}