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: 59447ba0c57eb1e485bbbdb4963edd7f7b605c24177e172a10e15114193f7a77
Tx prefix hash: f6dd8bc8829e1136a39511cda8291be0705991dc564549abe8696d826ef7b84d
Tx public key: 6d5d7be906ad557341975ac96682a4765997e40963fd2fe8b64f6a72971b28c6
| Timestamp: 1779874488 | Timestamp [UTC]: 2026-05-27 09:34:48 | Age [y:d:h:m:s]: 00:012:16:01:09 |
| Block: 2861 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5025 | RingCT/type: yes/0 |
| Extra: 016d5d7be906ad557341975ac96682a4765997e40963fd2fe8b64f6a72971b28c602090000000226697be300 | ||
1 output(s) for total of 34.992963099667 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7a36d421b2f1768d4f17cac05a0dbe53e0e4bc8a9575ce57a78fcfef6739e276 | 34.992963099667 | 3387 of 0 | <7e> |
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": 2921,
"vin": [ {
"gen": {
"height": 2861
}
}
],
"vout": [ {
"amount": 34992963099667,
"target": {
"tagged_key": {
"key": "7a36d421b2f1768d4f17cac05a0dbe53e0e4bc8a9575ce57a78fcfef6739e276",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 109, 93, 123, 233, 6, 173, 85, 115, 65, 151, 90, 201, 102, 130, 164, 118, 89, 151, 228, 9, 99, 253, 47, 232, 182, 79, 106, 114, 151, 27, 40, 198, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}