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: bb325f40e49ae870c1a24725aa167a8610ddf87b6c9057bbbd85258dc3b0f401
Tx prefix hash: 77a11f178b024effd80e172346c08307909a8bbbc787a05d0cfe237ecd76917e
Tx public key: 144fba84c87156f8528f96ede0b3c86cf5468b57d9d18415d06729b6aa5943df
| Timestamp: 1780899381 | Timestamp [UTC]: 2026-06-08 06:16:21 | Age [y:d:h:m:s]: 00:000:18:06:48 |
| Block: 7800 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 86 | RingCT/type: yes/0 |
| Extra: 01144fba84c87156f8528f96ede0b3c86cf5468b57d9d18415d06729b6aa5943df0209000000014a728a4c00 | ||
1 output(s) for total of 34.664863097929 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97b151db49fe22cb39be6aeb860f13be1dcb8a1ea25a3955b5636b8ce741b1e5 | 34.664863097929 | 9666 of 0 | <b7> |
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": 7860,
"vin": [ {
"gen": {
"height": 7800
}
}
],
"vout": [ {
"amount": 34664863097929,
"target": {
"tagged_key": {
"key": "97b151db49fe22cb39be6aeb860f13be1dcb8a1ea25a3955b5636b8ce741b1e5",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 20, 79, 186, 132, 200, 113, 86, 248, 82, 143, 150, 237, 224, 179, 200, 108, 245, 70, 139, 87, 217, 209, 132, 21, 208, 103, 41, 182, 170, 89, 67, 223, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}