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: 05bbfe0b94972618712d33aaed8fb13faa0886527097e5701981250fc4edb110
Tx prefix hash: cf6fa0af21c7e00b519368455951b2f42dc66371c93e76c67d7ba431cb4eaf7f
Tx public key: 005500bf7f134a2660e8cd9c3143ddd5bdfda283082816250fd1dccea6d5e00d
| Timestamp: 1780803048 | Timestamp [UTC]: 2026-06-07 03:30:48 | Age [y:d:h:m:s]: 00:001:23:09:48 |
| Block: 6875 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1022 | RingCT/type: yes/0 |
| Extra: 01005500bf7f134a2660e8cd9c3143ddd5bdfda283082816250fd1dccea6d5e00d020900000001e49593ff00 | ||
1 output(s) for total of 34.726076270345 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6fa1efc9e8fa6a1fd6ba674cbb94cfa328c623866179b69250dd474b4c6f4d6f | 34.726076270345 | 8487 of 0 | <d9> |
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": 6935,
"vin": [ {
"gen": {
"height": 6875
}
}
],
"vout": [ {
"amount": 34726076270345,
"target": {
"tagged_key": {
"key": "6fa1efc9e8fa6a1fd6ba674cbb94cfa328c623866179b69250dd474b4c6f4d6f",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 0, 85, 0, 191, 127, 19, 74, 38, 96, 232, 205, 156, 49, 67, 221, 213, 189, 253, 162, 131, 8, 40, 22, 37, 15, 209, 220, 206, 166, 213, 224, 13, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}