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: f293384f8daf548a1b352901ee23c952522e8f1fed3f7fce8fa00c496449c978
Tx prefix hash: 96e158b5359e3c51f20db096411642da0bf9e6247a1422b4ba46bbf2e9f32ba5
Tx public key: f53f64a87c1e41c421806b644a55ff7f56087df6ec50e9d2ba46372a52209389
| Timestamp: 1780690116 | Timestamp [UTC]: 2026-06-05 20:08:36 | Age [y:d:h:m:s]: 00:003:04:38:11 |
| Block: 5636 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2250 | RingCT/type: yes/0 |
| Extra: 01f53f64a87c1e41c421806b644a55ff7f56087df6ec50e9d2ba46372a52209389020900000001e49593ff00 | ||
1 output(s) for total of 34.808238228783 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0624191ea4b80ada0faf41344362e4308c18c5da8581ce9c86a1ea99678d675c | 34.808238228783 | 7083 of 0 | <62> |
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": 5696,
"vin": [ {
"gen": {
"height": 5636
}
}
],
"vout": [ {
"amount": 34808238228783,
"target": {
"tagged_key": {
"key": "0624191ea4b80ada0faf41344362e4308c18c5da8581ce9c86a1ea99678d675c",
"view_tag": "62"
}
}
}
],
"extra": [ 1, 245, 63, 100, 168, 124, 30, 65, 196, 33, 128, 107, 100, 74, 85, 255, 127, 86, 8, 125, 246, 236, 80, 233, 210, 186, 70, 55, 42, 82, 32, 147, 137, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}