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: 4c9e8d3aeb1f356eb6c827e4a5a7e07d6f6bfe00c3ee5547cfc1a6c986ca7881
Tx prefix hash: 4e99a345923177f3b0a9874994b738b4520cb2d8daf90ef317184178a0f6b0e5
Tx public key: 806a149734b71f791c54465e948413991d2beab11934b3fa55965f48c54f73f4
| Timestamp: 1779448077 | Timestamp [UTC]: 2026-05-22 11:07:57 | Age [y:d:h:m:s]: 00:017:12:10:56 |
| Block: 295 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7591 | RingCT/type: yes/0 |
| Extra: 01806a149734b71f791c54465e948413991d2beab11934b3fa55965f48c54f73f40209000000014438f87f00 | ||
1 output(s) for total of 35.164647594994 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09fcf8711a3c045ba36dc3cabd47be4fd755a5b3383d72226193c1e0cb4f6ba2 | 35.164647594994 | 291 of 0 | <00> |
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": 355,
"vin": [ {
"gen": {
"height": 295
}
}
],
"vout": [ {
"amount": 35164647594994,
"target": {
"tagged_key": {
"key": "09fcf8711a3c045ba36dc3cabd47be4fd755a5b3383d72226193c1e0cb4f6ba2",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 128, 106, 20, 151, 52, 183, 31, 121, 28, 84, 70, 94, 148, 132, 19, 153, 29, 43, 234, 177, 25, 52, 179, 250, 85, 150, 95, 72, 197, 79, 115, 244, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}