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: 7a55c1fc617c37f6b96b2892a1205d584ede52d4bfdc01057335d0b69b64d3e4
Tx prefix hash: 87d3cc8146e77b225ee097f3344139401cac69b77bc987a7cb1de4bb5a6bafb8
Tx public key: 597c0b4a3d0031b315cd724f8ff13e4e4931f457587858e1848a36c63d2b5ca1
| Timestamp: 1779637713 | Timestamp [UTC]: 2026-05-24 15:48:33 | Age [y:d:h:m:s]: 00:015:09:47:24 |
| Block: 1168 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6718 | RingCT/type: yes/0 |
| Extra: 01597c0b4a3d0031b315cd724f8ff13e4e4931f457587858e1848a36c63d2b5ca1020900000001ba6d17be00 | ||
1 output(s) for total of 35.106143066397 HMNY
| stealth address | amount | amount idx | tag |
| 00: af1db9b4231e210270aec4f55f9e9ad72b4882d52c4aeb0b42803912de465606 | 35.106143066397 | 1310 of 0 | <9d> |
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": 1228,
"vin": [ {
"gen": {
"height": 1168
}
}
],
"vout": [ {
"amount": 35106143066397,
"target": {
"tagged_key": {
"key": "af1db9b4231e210270aec4f55f9e9ad72b4882d52c4aeb0b42803912de465606",
"view_tag": "9d"
}
}
}
],
"extra": [ 1, 89, 124, 11, 74, 61, 0, 49, 179, 21, 205, 114, 79, 143, 241, 62, 78, 73, 49, 244, 87, 88, 120, 88, 225, 132, 138, 54, 198, 61, 43, 92, 161, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}