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: 8bd627e0d2ad4c716045c97031e22c6f1c3bb9ede139571784cb369f7f3aca6e
Tx prefix hash: cfb1a24d269b9fc8477601ae6906f06290294ade9ee0558bee5033608970150b
Tx public key: e61c91b0f8c8f59f181a44fc03cad20ad0a4a2d84655663d9bd754c7d4d010ea
| Timestamp: 1780055285 | Timestamp [UTC]: 2026-05-29 11:48:05 | Age [y:d:h:m:s]: 00:010:11:30:48 |
| Block: 4446 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3440 | RingCT/type: yes/0 |
| Extra: 01e61c91b0f8c8f59f181a44fc03cad20ad0a4a2d84655663d9bd754c7d4d010ea02090000000126697be300 | ||
1 output(s) for total of 34.887333853962 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2036be7e145993002db20f48d96accdd5af264f466aadf340ceb26fa1bc75664 | 34.887333853962 | 5564 of 0 | <d1> |
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": 4506,
"vin": [ {
"gen": {
"height": 4446
}
}
],
"vout": [ {
"amount": 34887333853962,
"target": {
"tagged_key": {
"key": "2036be7e145993002db20f48d96accdd5af264f466aadf340ceb26fa1bc75664",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 230, 28, 145, 176, 248, 200, 245, 159, 24, 26, 68, 252, 3, 202, 210, 10, 208, 164, 162, 216, 70, 85, 102, 61, 155, 215, 84, 199, 212, 208, 16, 234, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}