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: 1ffd504f0d05802f290b1f29f829ed526ecf01f3f3888e678ebda90df9fffb4a
Tx prefix hash: f791b6a94a7b5328ac3bd984090a164bf02fffe5740220a0db4ff3045f2e1e36
Tx public key: d27d5a569ee6bc7244b8a9c9d96fd41ddde3f8084337e1fe3309d47a1be89468
| Timestamp: 1781023187 | Timestamp [UTC]: 2026-06-09 16:39:47 | Age [y:d:h:m:s]: 00:006:02:42:22 |
| Block: 8718 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 27 | RingCT/type: yes/0 |
| Extra: 01d27d5a569ee6bc7244b8a9c9d96fd41ddde3f8084337e1fe3309d47a1be89468020900000001e49593ff00 | ||
1 output(s) for total of 34.611641842184 HMNY
| stealth address | amount | amount idx | tag |
| 00: 281e17da87ae1f118395ea04b30edbf5a0a089fb76b3ed3ca308f53d7503bdf2 | 34.611641842184 | 10780 of 0 | <ce> |
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": 8778,
"vin": [ {
"gen": {
"height": 8718
}
}
],
"vout": [ {
"amount": 34611641842184,
"target": {
"tagged_key": {
"key": "281e17da87ae1f118395ea04b30edbf5a0a089fb76b3ed3ca308f53d7503bdf2",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 210, 125, 90, 86, 158, 230, 188, 114, 68, 184, 169, 201, 217, 111, 212, 29, 221, 227, 248, 8, 67, 55, 225, 254, 51, 9, 212, 122, 27, 232, 148, 104, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}