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: f351cab1ce72a69a9a8c09cf010ea508734bfff2f19b344dfd1202eb46416f72
Tx prefix hash: 7300bce6fb801f369bd6314cbd60d9d31dc8811ea7c6c6b406e08c32e9092f0f
Tx public key: 8847022058225174294ef66e4fec3fcf525f8e73e80cb199f49e7a13ae657864
| Timestamp: 1779848087 | Timestamp [UTC]: 2026-05-27 02:14:47 | Age [y:d:h:m:s]: 00:012:23:21:10 |
| Block: 2492 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5394 | RingCT/type: yes/0 |
| Extra: 018847022058225174294ef66e4fec3fcf525f8e73e80cb199f49e7a13ae65786402090000000226697be300 | ||
1 output(s) for total of 35.017600247041 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9decd0b94138c9e04ff8527ab125ea626f8c862ab1fe1cdee03d84ee93bead16 | 35.017600247041 | 2930 of 0 | <87> |
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": 2552,
"vin": [ {
"gen": {
"height": 2492
}
}
],
"vout": [ {
"amount": 35017600247041,
"target": {
"tagged_key": {
"key": "9decd0b94138c9e04ff8527ab125ea626f8c862ab1fe1cdee03d84ee93bead16",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 136, 71, 2, 32, 88, 34, 81, 116, 41, 78, 246, 110, 79, 236, 63, 207, 82, 95, 142, 115, 232, 12, 177, 153, 244, 158, 122, 19, 174, 101, 120, 100, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}