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: 129f8830777f34f7fc9ac2d0f01c30247e2c9a9248b54b756a42c7f46dead9d5
Tx prefix hash: 4c645a8f84304ce069c4d68d9bea1fe0fe427f752b3535f6c53ea8434bf7210c
Tx public key: 2c960fcd1afd627d5b22d56fb4ac99d8f8e9c48e1189bdb06a7092adfdd70f61
| Timestamp: 1780692925 | Timestamp [UTC]: 2026-06-05 20:55:25 | Age [y:d:h:m:s]: 00:003:05:54:23 |
| Block: 5831 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2069 | RingCT/type: yes/0 |
| Extra: 012c960fcd1afd627d5b22d56fb4ac99d8f8e9c48e1189bdb06a7092adfdd70f61020900000001e49593ff00 | ||
1 output(s) for total of 34.795294291835 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4bcf16c510b31f4869febaa46b9c03340dc0e72863b38ef4a380c36114306f9c | 34.795294291835 | 7288 of 0 | <bb> |
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": 5891,
"vin": [ {
"gen": {
"height": 5831
}
}
],
"vout": [ {
"amount": 34795294291835,
"target": {
"tagged_key": {
"key": "4bcf16c510b31f4869febaa46b9c03340dc0e72863b38ef4a380c36114306f9c",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 44, 150, 15, 205, 26, 253, 98, 125, 91, 34, 213, 111, 180, 172, 153, 216, 248, 233, 196, 142, 17, 137, 189, 176, 106, 112, 146, 173, 253, 215, 15, 97, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}