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: 20bb092b745e4b33ecf191c1f2349a4baf2f028099aba8ba0d0264f71ffe057a
Tx prefix hash: 3eed9dd88dd7ee2f08d9a2e2d8e3c815d9dc726ab76f9e10cff3a9f90732826d
Tx public key: 4c1a982a40d8671a00d50770e9e91437567f56d9d1bb209798796a4b724ad8c4
| Timestamp: 1781001546 | Timestamp [UTC]: 2026-06-09 10:39:06 | Age [y:d:h:m:s]: 00:000:06:29:57 |
| Block: 8460 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 271 | RingCT/type: yes/0 |
| Extra: 014c1a982a40d8671a00d50770e9e91437567f56d9d1bb209798796a4b724ad8c4020900000002e49593ff00 | ||
1 output(s) for total of 34.621252645313 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb72911668aecc6fa3e1b30482276ba45fac000d28a443d00f1fb21a04275da3 | 34.621252645313 | 10452 of 0 | <40> |
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": 8520,
"vin": [ {
"gen": {
"height": 8460
}
}
],
"vout": [ {
"amount": 34621252645313,
"target": {
"tagged_key": {
"key": "bb72911668aecc6fa3e1b30482276ba45fac000d28a443d00f1fb21a04275da3",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 76, 26, 152, 42, 64, 216, 103, 26, 0, 213, 7, 112, 233, 233, 20, 55, 86, 127, 86, 217, 209, 187, 32, 151, 152, 121, 106, 75, 114, 74, 216, 196, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}