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: 61b9b1480fb61663dd63d3e7fc4fdd2b6cb651fb6d6c8fdf1c6aef9413dec73b
Tx prefix hash: 144bb3815658e9ad53a7db06e4f7e6964dfc1c28084200771ee610830d953a42
Tx public key: 42060991b38e8a1d02df74187626933e3fcba537be87ba45e65004c6e361e3f0
| Timestamp: 1780055310 | Timestamp [UTC]: 2026-05-29 11:48:30 | Age [y:d:h:m:s]: 00:011:05:20:33 |
| Block: 4447 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4288 | RingCT/type: yes/0 |
| Extra: 0142060991b38e8a1d02df74187626933e3fcba537be87ba45e65004c6e361e3f002090000000526697be300 | ||
1 output(s) for total of 34.893887711654 HMNY
| stealth address | amount | amount idx | tag |
| 00: 131de3781dccf4da704b25846a3988efba73e513224e8e0cf9820f11b80f0216 | 34.893887711654 | 5565 of 0 | <6b> |
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": 4507,
"vin": [ {
"gen": {
"height": 4447
}
}
],
"vout": [ {
"amount": 34893887711654,
"target": {
"tagged_key": {
"key": "131de3781dccf4da704b25846a3988efba73e513224e8e0cf9820f11b80f0216",
"view_tag": "6b"
}
}
}
],
"extra": [ 1, 66, 6, 9, 145, 179, 142, 138, 29, 2, 223, 116, 24, 118, 38, 147, 62, 63, 203, 165, 55, 190, 135, 186, 69, 230, 80, 4, 198, 227, 97, 227, 240, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}