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: 4eea16e92fb093d0dbc72954c52c8c49bdebcfb3798ffa825660bb4332cdea6d
Tx prefix hash: 6afaca58698a16ab9c662f80a00dfee00ba97d245e9c0c35b51ed2f03357e8a5
Tx public key: bbe53ff28ace19c3bce11852eee6eb0a4e9d5e8dd8ffe550e0cf57eba2531193
| Timestamp: 1779447887 | Timestamp [UTC]: 2026-05-22 11:04:47 | Age [y:d:h:m:s]: 00:018:06:04:16 |
| Block: 293 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8441 | RingCT/type: yes/0 |
| Extra: 01bbe53ff28ace19c3bce11852eee6eb0a4e9d5e8dd8ffe550e0cf57eba25311930209000000064438f87f00 | ||
1 output(s) for total of 35.164781737863 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad841bb928b623fa1da45f70241905eb7f654a207a142ef54fa2afa1903394a7 | 35.164781737863 | 289 of 0 | <ef> |
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": 353,
"vin": [ {
"gen": {
"height": 293
}
}
],
"vout": [ {
"amount": 35164781737863,
"target": {
"tagged_key": {
"key": "ad841bb928b623fa1da45f70241905eb7f654a207a142ef54fa2afa1903394a7",
"view_tag": "ef"
}
}
}
],
"extra": [ 1, 187, 229, 63, 242, 138, 206, 25, 195, 188, 225, 24, 82, 238, 230, 235, 10, 78, 157, 94, 141, 216, 255, 229, 80, 224, 207, 87, 235, 162, 83, 17, 147, 2, 9, 0, 0, 0, 6, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}