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: bc09670a1a55cd216f497726041aa8e298813dbb05eaf615eec8ac085a3c5f1a
Tx prefix hash: 5bc6b8b5aa3e2601171e12d6f32e7fe7f00861160e91f2c9aa8a4611e99b88af
Tx public key: 0db6698a459293d2190e763b3e47ff212f91d21d9325e5aa3b49fa43d1c80676
| Timestamp: 1779845467 | Timestamp [UTC]: 2026-05-27 01:31:07 | Age [y:d:h:m:s]: 00:021:10:04:58 |
| Block: 2443 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6302 | RingCT/type: yes/0 |
| Extra: 010db6698a459293d2190e763b3e47ff212f91d21d9325e5aa3b49fa43d1c8067602090000000226697be300 | ||
1 output(s) for total of 35.020873150929 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b79ef45f36ee9d6a22bf6c3bbca29beaefed6cbcfe2d19d5a9ea217c10c2bd9 | 35.020873150929 | 2873 of 0 | <1f> |
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": 2503,
"vin": [ {
"gen": {
"height": 2443
}
}
],
"vout": [ {
"amount": 35020873150929,
"target": {
"tagged_key": {
"key": "3b79ef45f36ee9d6a22bf6c3bbca29beaefed6cbcfe2d19d5a9ea217c10c2bd9",
"view_tag": "1f"
}
}
}
],
"extra": [ 1, 13, 182, 105, 138, 69, 146, 147, 210, 25, 14, 118, 59, 62, 71, 255, 33, 47, 145, 210, 29, 147, 37, 229, 170, 59, 73, 250, 67, 209, 200, 6, 118, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}