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: 87601b72df704ad89abe378d933ce46ec0a7d442634b32558bd3f5a5a7b58604
Tx prefix hash: 993e913a465d80146619bce964bfdfb9f6ca7462054d6cf4c3671db116618229
Tx public key: 9dc033618d12bf24bbc398f0b78d3e63e0fa6aaf9d896cca039230a168759b4a
| Timestamp: 1780978622 | Timestamp [UTC]: 2026-06-09 04:17:02 | Age [y:d:h:m:s]: 00:000:08:20:43 |
| Block: 7982 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 592 | RingCT/type: yes/0 |
| Extra: 019dc033618d12bf24bbc398f0b78d3e63e0fa6aaf9d896cca039230a168759b4a020900000001e49593ff00 | ||
1 output(s) for total of 34.652831702629 HMNY
| stealth address | amount | amount idx | tag |
| 00: 44855b240ea6ff53a8d5929ca1c4380fb005635c0edbbf45c5f160c3808a5033 | 34.652831702629 | 9898 of 0 | <92> |
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": 8042,
"vin": [ {
"gen": {
"height": 7982
}
}
],
"vout": [ {
"amount": 34652831702629,
"target": {
"tagged_key": {
"key": "44855b240ea6ff53a8d5929ca1c4380fb005635c0edbbf45c5f160c3808a5033",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 157, 192, 51, 97, 141, 18, 191, 36, 187, 195, 152, 240, 183, 141, 62, 99, 224, 250, 106, 175, 157, 137, 108, 202, 3, 146, 48, 161, 104, 117, 155, 74, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}