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: 18ac57d7a6d2dc616608575b1771b06938df3ee001e6fd5e49f8d6f53a163acb
Tx prefix hash: 0ac4e58d618d3434e0f957b5393fa79e1fd78c0b10e00ad4eaa869d09fc1f4b9
Tx public key: 6e6f4e3e1b691813c4d77100194d07a9459edf2664179bbfd81cefc818f6f585
| Timestamp: 1780699585 | Timestamp [UTC]: 2026-06-05 22:46:25 | Age [y:d:h:m:s]: 00:003:02:00:22 |
| Block: 6035 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1851 | RingCT/type: yes/0 |
| Extra: 016e6f4e3e1b691813c4d77100194d07a9459edf2664179bbfd81cefc818f6f585020900000001e49593ff00 | ||
1 output(s) for total of 34.781758094131 HMNY
| stealth address | amount | amount idx | tag |
| 00: 154dab2ea9dff4776887b63b114bc61099407943ee4c0483f247dc6847ad9303 | 34.781758094131 | 7504 of 0 | <61> |
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": 6095,
"vin": [ {
"gen": {
"height": 6035
}
}
],
"vout": [ {
"amount": 34781758094131,
"target": {
"tagged_key": {
"key": "154dab2ea9dff4776887b63b114bc61099407943ee4c0483f247dc6847ad9303",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 110, 111, 78, 62, 27, 105, 24, 19, 196, 215, 113, 0, 25, 77, 7, 169, 69, 158, 223, 38, 100, 23, 155, 191, 216, 28, 239, 200, 24, 246, 245, 133, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}