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: b497de142b6eec22aeebd374aedc6173e905cfeff4f67f3f2974d1b9a4a56bd3
Tx prefix hash: 8e5cda1b70affe18ff158facb81d23ef1454d91f5535e157fe4f05fc52c22800
Tx public key: 4d8fb309fb4f440bba64fc13a3417cf5b23713b783f250d4665332da50fbf937
| Timestamp: 1780987035 | Timestamp [UTC]: 2026-06-09 06:37:15 | Age [y:d:h:m:s]: 00:000:08:11:40 |
| Block: 8162 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 478 | RingCT/type: yes/0 |
| Extra: 014d8fb309fb4f440bba64fc13a3417cf5b23713b783f250d4665332da50fbf937020900000002e49593ff00 | ||
1 output(s) for total of 34.640936627716 HMNY
| stealth address | amount | amount idx | tag |
| 00: df1644c9f8ea56eeb91fc4fd2fd5d96dd628eb9f53942534b8a17b4ed406bd6e | 34.640936627716 | 10106 of 0 | <82> |
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": 8222,
"vin": [ {
"gen": {
"height": 8162
}
}
],
"vout": [ {
"amount": 34640936627716,
"target": {
"tagged_key": {
"key": "df1644c9f8ea56eeb91fc4fd2fd5d96dd628eb9f53942534b8a17b4ed406bd6e",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 77, 143, 179, 9, 251, 79, 68, 11, 186, 100, 252, 19, 163, 65, 124, 245, 178, 55, 19, 183, 131, 242, 80, 212, 102, 83, 50, 218, 80, 251, 249, 55, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}