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: a938d6f0c40460aac5212970913eb6268767800e84f5f2a98a57d7d26ca3f7dc
Tx prefix hash: 1681c6c0be3e11cbec996624142fb5c122c29240ffccc48ab66d849193b2a6cc
Tx public key: cd3c5104c8f1a208a654d9fb73f9ceca359268d2108d86508a6d9faef7368c12
| Timestamp: 1781005080 | Timestamp [UTC]: 2026-06-09 11:38:00 | Age [y:d:h:m:s]: 00:005:23:36:00 |
| Block: 8521 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 224 | RingCT/type: yes/0 |
| Extra: 01cd3c5104c8f1a208a654d9fb73f9ceca359268d2108d86508a6d9faef7368c12020900000002e49593ff00 | ||
1 output(s) for total of 34.617224753063 HMNY
| stealth address | amount | amount idx | tag |
| 00: 020e75de849c9ce523413abdd45d486171138803baadef905ddd2db70d241e65 | 34.617224753063 | 10525 of 0 | <68> |
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": 8581,
"vin": [ {
"gen": {
"height": 8521
}
}
],
"vout": [ {
"amount": 34617224753063,
"target": {
"tagged_key": {
"key": "020e75de849c9ce523413abdd45d486171138803baadef905ddd2db70d241e65",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 205, 60, 81, 4, 200, 241, 162, 8, 166, 84, 217, 251, 115, 249, 206, 202, 53, 146, 104, 210, 16, 141, 134, 80, 138, 109, 159, 174, 247, 54, 140, 18, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}