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: 2c98fbef574b925ada8b0d35a183c66da76363618a3eae10afd6437d10bec264
Tx prefix hash: 499980945a4539076dc3c4dc77a07eae815dd6ea73c4679f37d9f500c4b46ea1
Tx public key: b353f37d3656f0187a49aedaf66662c9cffb5d911d8e8ba0e18e1af76d9b784e
| Timestamp: 1780086089 | Timestamp [UTC]: 2026-05-29 20:21:29 | Age [y:d:h:m:s]: 00:018:12:42:28 |
| Block: 4813 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3932 | RingCT/type: yes/0 |
| Extra: 01b353f37d3656f0187a49aedaf66662c9cffb5d911d8e8ba0e18e1af76d9b784e02090000000126697be300 | ||
1 output(s) for total of 34.867135748787 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ba8f9920f0d4fb28538d4a5ee7879532445fc762c903b1b2905bf9a14135512 | 34.867135748787 | 6053 of 0 | <08> |
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": 4873,
"vin": [ {
"gen": {
"height": 4813
}
}
],
"vout": [ {
"amount": 34867135748787,
"target": {
"tagged_key": {
"key": "4ba8f9920f0d4fb28538d4a5ee7879532445fc762c903b1b2905bf9a14135512",
"view_tag": "08"
}
}
}
],
"extra": [ 1, 179, 83, 243, 125, 54, 86, 240, 24, 122, 73, 174, 218, 246, 102, 98, 201, 207, 251, 93, 145, 29, 142, 139, 160, 225, 142, 26, 247, 109, 155, 120, 78, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}