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: 7911a68d2260de3d9955ea2395d5243d4552156ccfa88a61982576f35d9bb2b3
Tx prefix hash: 72717a891601f24e56d738352b951d1db517ec516255a94414182d9e3d387f9b
Tx public key: d8f69f7389610328cdb98e9606a58ac8d9c6155356adb3ff4704a34a41d6e7ef
| Timestamp: 1780088202 | Timestamp [UTC]: 2026-05-29 20:56:42 | Age [y:d:h:m:s]: 00:010:05:43:54 |
| Block: 4829 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3068 | RingCT/type: yes/0 |
| Extra: 01d8f69f7389610328cdb98e9606a58ac8d9c6155356adb3ff4704a34a41d6e7ef02090000000626697be300 | ||
1 output(s) for total of 34.861857432081 HMNY
| stealth address | amount | amount idx | tag |
| 00: ea51dec2f3a93bece8d3eca1a571f4cb4a147221a63aed7037d8c30ba969ce3d | 34.861857432081 | 6077 of 0 | <24> |
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": 4889,
"vin": [ {
"gen": {
"height": 4829
}
}
],
"vout": [ {
"amount": 34861857432081,
"target": {
"tagged_key": {
"key": "ea51dec2f3a93bece8d3eca1a571f4cb4a147221a63aed7037d8c30ba969ce3d",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 216, 246, 159, 115, 137, 97, 3, 40, 205, 185, 142, 150, 6, 165, 138, 200, 217, 198, 21, 83, 86, 173, 179, 255, 71, 4, 163, 74, 65, 214, 231, 239, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}