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: e021af5c117eb9c5ff97878ceafa6fe6d6d253550ecdb76997178529a0550867
Tx prefix hash: 51bc8b975d1c41df9c5fedf89978426cd75c1dc98d7bfe95f25667b19aa35c22
Tx public key: 59664ffc12a06d69ec1846d7eb74d5ef49ee80cae84c7d2463b2296cef8613a5
| Timestamp: 1781018597 | Timestamp [UTC]: 2026-06-09 15:23:17 | Age [y:d:h:m:s]: 00:006:00:15:34 |
| Block: 8661 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 84 | RingCT/type: yes/0 |
| Extra: 0159664ffc12a06d69ec1846d7eb74d5ef49ee80cae84c7d2463b2296cef8613a5020900000001e49593ff00 | ||
1 output(s) for total of 34.607982182037 HMNY
| stealth address | amount | amount idx | tag |
| 00: a8c70e56256af6e4bcabaf188833c1cf494d0d627ec2b5757d405dea39b20c0e | 34.607982182037 | 10709 of 0 | <2f> |
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": 8721,
"vin": [ {
"gen": {
"height": 8661
}
}
],
"vout": [ {
"amount": 34607982182037,
"target": {
"tagged_key": {
"key": "a8c70e56256af6e4bcabaf188833c1cf494d0d627ec2b5757d405dea39b20c0e",
"view_tag": "2f"
}
}
}
],
"extra": [ 1, 89, 102, 79, 252, 18, 160, 109, 105, 236, 24, 70, 215, 235, 116, 213, 239, 73, 238, 128, 202, 232, 76, 125, 36, 99, 178, 41, 108, 239, 134, 19, 165, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}