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: 0363721e893616bb916b9eb155f8673d6b1b6a5843baee743687ba85ec9f56fb
Tx prefix hash: 6e73749fedf882bcab935983264237941138db93a1e3cc6d4e23044c35d2767a
Tx public key: d21ba57b1c5ef5c15e5a5ea5721427ffca7728d4bed1d176a2f801baceeb8903
| Timestamp: 1780724261 | Timestamp [UTC]: 2026-06-06 05:37:41 | Age [y:d:h:m:s]: 00:002:19:58:16 |
| Block: 6265 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1621 | RingCT/type: yes/0 |
| Extra: 01d21ba57b1c5ef5c15e5a5ea5721427ffca7728d4bed1d176a2f801baceeb8903020900000002e49593ff00 | ||
1 output(s) for total of 34.766503010043 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2aaeede25dca436c71d8463987b57361cb5e5a88ee34b5ab726c42be91659628 | 34.766503010043 | 7748 of 0 | <ea> |
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": 6325,
"vin": [ {
"gen": {
"height": 6265
}
}
],
"vout": [ {
"amount": 34766503010043,
"target": {
"tagged_key": {
"key": "2aaeede25dca436c71d8463987b57361cb5e5a88ee34b5ab726c42be91659628",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 210, 27, 165, 123, 28, 94, 245, 193, 94, 90, 94, 165, 114, 20, 39, 255, 202, 119, 40, 212, 190, 209, 209, 118, 162, 248, 1, 186, 206, 235, 137, 3, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}