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: e8f8cbd394cf8300f4cff734a4da5b302d28fe14c6632436c79734aa80c94e3b
Tx prefix hash: 6998b373a202742527e2ee6da1ee752c672e6cd02f9efa9f44c897e643dc0c6a
Tx public key: 65d4e38866bb7ec26ea0b6ec74b651dcef2c77f9be62b2ae958928f018cf5ee7
| Timestamp: 1780059109 | Timestamp [UTC]: 2026-05-29 12:51:49 | Age [y:d:h:m:s]: 00:010:08:20:18 |
| Block: 4493 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3393 | RingCT/type: yes/0 |
| Extra: 0165d4e38866bb7ec26ea0b6ec74b651dcef2c77f9be62b2ae958928f018cf5ee702090000000326697be300 | ||
1 output(s) for total of 34.884206502657 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f43ccd019fb5732bfb4513c4470a6b621813a07d1f07bcec5f24add004fdffc | 34.884206502657 | 5632 of 0 | <ba> |
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": 4553,
"vin": [ {
"gen": {
"height": 4493
}
}
],
"vout": [ {
"amount": 34884206502657,
"target": {
"tagged_key": {
"key": "8f43ccd019fb5732bfb4513c4470a6b621813a07d1f07bcec5f24add004fdffc",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 101, 212, 227, 136, 102, 187, 126, 194, 110, 160, 182, 236, 116, 182, 81, 220, 239, 44, 119, 249, 190, 98, 178, 174, 149, 137, 40, 240, 24, 207, 94, 231, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}