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: 6e3a952d63e29cda816639b8f7915615e7dc2447048bce4dc419bbc9711d2e3a
Tx prefix hash: ff28037d0d416c5e548e36cf2950a9b6aec66dcd318c6b073e6cb0cd769da707
Tx public key: 5b662d785c5af6dc07d9348915d3630312c0410e2f2d8fed1191f89eec8a2d8d
| Timestamp: 1779478096 | Timestamp [UTC]: 2026-05-22 19:28:16 | Age [y:d:h:m:s]: 00:017:08:10:34 |
| Block: 629 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7316 | RingCT/type: yes/0 |
| Extra: 015b662d785c5af6dc07d9348915d3630312c0410e2f2d8fed1191f89eec8a2d8d02090000000293369e7d00 | ||
1 output(s) for total of 35.142252912710 HMNY
| stealth address | amount | amount idx | tag |
| 00: e856959cb1ef60da558ea08399caee13f04e500548526e56f2b7b471c9e4c087 | 35.142252912710 | 660 of 0 | <12> |
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": 689,
"vin": [ {
"gen": {
"height": 629
}
}
],
"vout": [ {
"amount": 35142252912710,
"target": {
"tagged_key": {
"key": "e856959cb1ef60da558ea08399caee13f04e500548526e56f2b7b471c9e4c087",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 91, 102, 45, 120, 92, 90, 246, 220, 7, 217, 52, 137, 21, 211, 99, 3, 18, 192, 65, 14, 47, 45, 143, 237, 17, 145, 248, 158, 236, 138, 45, 141, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}