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: dc769d2c6d36450455a5b3c42b3dea32766d8de8c6e69a309a91839648222738
Tx prefix hash: 23f359ba022cbf7bdb13aa73391fd76593f9a77f6332d394df09b34aa4be47e6
Tx public key: e66ecbc9d317a8b8fca8d9d9394d0909b8bc81c160d4855ccd3b1b8b3884ee8d
| Timestamp: 1780054780 | Timestamp [UTC]: 2026-05-29 11:39:40 | Age [y:d:h:m:s]: 00:010:11:39:13 |
| Block: 4438 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3448 | RingCT/type: yes/0 |
| Extra: 01e66ecbc9d317a8b8fca8d9d9394d0909b8bc81c160d4855ccd3b1b8b3884ee8d02090000000126697be300 | ||
1 output(s) for total of 34.887866197000 HMNY
| stealth address | amount | amount idx | tag |
| 00: 853dc8466f52b6c9c53dce2dd411d722b818c7c02e0086380a5c3f251f4903b8 | 34.887866197000 | 5556 of 0 | <68> |
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": 4498,
"vin": [ {
"gen": {
"height": 4438
}
}
],
"vout": [ {
"amount": 34887866197000,
"target": {
"tagged_key": {
"key": "853dc8466f52b6c9c53dce2dd411d722b818c7c02e0086380a5c3f251f4903b8",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 230, 110, 203, 201, 211, 23, 168, 184, 252, 168, 217, 217, 57, 77, 9, 9, 184, 188, 129, 193, 96, 212, 133, 92, 205, 59, 27, 139, 56, 132, 238, 141, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}