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: ff759b8be716b59d7c0209458c3c6bda4bdaf92262680fc007518f8772978bfc
Tx prefix hash: bb1f151df059c193c73ffe71f96af3339e91f2dc09ce2fe058914450257a55cd
Tx public key: 9d97e8a72a3b47bb1a79489aec08b4f44406a2fb501cc4f9f2587f87a78b815a
| Timestamp: 1779840243 | Timestamp [UTC]: 2026-05-27 00:04:03 | Age [y:d:h:m:s]: 00:013:01:31:54 |
| Block: 2382 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5504 | RingCT/type: yes/0 |
| Extra: 019d97e8a72a3b47bb1a79489aec08b4f44406a2fb501cc4f9f2587f87a78b815a02090000000126697be300 | ||
1 output(s) for total of 35.024948009748 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3a89b5a8b272eda64b3847e2f790df9b2bad2ce2ae52f6f96b44844367b857da | 35.024948009748 | 2794 of 0 | <60> |
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": 2442,
"vin": [ {
"gen": {
"height": 2382
}
}
],
"vout": [ {
"amount": 35024948009748,
"target": {
"tagged_key": {
"key": "3a89b5a8b272eda64b3847e2f790df9b2bad2ce2ae52f6f96b44844367b857da",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 157, 151, 232, 167, 42, 59, 71, 187, 26, 121, 72, 154, 236, 8, 180, 244, 68, 6, 162, 251, 80, 28, 196, 249, 242, 88, 127, 135, 167, 139, 129, 90, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}