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: 86cef1468c58a944039cf04a3a101e3168a94715b3debb9a9ccd99c81ae65d99
Tx prefix hash: b3586b26233065bffc68aae64ce7ada81c7b84ca10e7f8d2b126faf5804edfc3
Tx public key: 0f91c5fd70f15a436d17d449f8031b87a0b86154cae3d8c878f4b75f6120c7da
| Timestamp: 1779468766 | Timestamp [UTC]: 2026-05-22 16:52:46 | Age [y:d:h:m:s]: 00:017:07:54:01 |
| Block: 541 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7345 | RingCT/type: yes/0 |
| Extra: 010f91c5fd70f15a436d17d449f8031b87a0b86154cae3d8c878f4b75f6120c7da02090000000893369e7d00 | ||
1 output(s) for total of 35.148151923855 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70de131c0e388ad3d1354f959464d8c7eea99989257d3245d79c9a7b1c609c89 | 35.148151923855 | 545 of 0 | <c2> |
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": 601,
"vin": [ {
"gen": {
"height": 541
}
}
],
"vout": [ {
"amount": 35148151923855,
"target": {
"tagged_key": {
"key": "70de131c0e388ad3d1354f959464d8c7eea99989257d3245d79c9a7b1c609c89",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 15, 145, 197, 253, 112, 241, 90, 67, 109, 23, 212, 73, 248, 3, 27, 135, 160, 184, 97, 84, 202, 227, 216, 200, 120, 244, 183, 95, 97, 32, 199, 218, 2, 9, 0, 0, 0, 8, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}