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: c0f9be77187bdefe59e130307e8e36a4c892a2216f9bfb559d95269459eb34b4
Tx prefix hash: 51332ec554e9bb831231003854a47ba18c83fecae78456a94616606102f5fdc1
Tx public key: 8e8b429939eec686a25b1d74dc1eb415f04d9cf0b82d03396998840fa1ed7a84
| Timestamp: 1780769360 | Timestamp [UTC]: 2026-06-06 18:09:20 | Age [y:d:h:m:s]: 00:002:06:37:27 |
| Block: 6651 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1235 | RingCT/type: yes/0 |
| Extra: 018e8b429939eec686a25b1d74dc1eb415f04d9cf0b82d03396998840fa1ed7a84020900000001e49593ff00 | ||
1 output(s) for total of 34.740916034825 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0eda78d88cef68d79d15b75fc47efa0828351a7cc3923ee5d7d5cf6fb768ac36 | 34.740916034825 | 8199 of 0 | <65> |
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": 6711,
"vin": [ {
"gen": {
"height": 6651
}
}
],
"vout": [ {
"amount": 34740916034825,
"target": {
"tagged_key": {
"key": "0eda78d88cef68d79d15b75fc47efa0828351a7cc3923ee5d7d5cf6fb768ac36",
"view_tag": "65"
}
}
}
],
"extra": [ 1, 142, 139, 66, 153, 57, 238, 198, 134, 162, 91, 29, 116, 220, 30, 180, 21, 240, 77, 156, 240, 184, 45, 3, 57, 105, 152, 132, 15, 161, 237, 122, 132, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}