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: 1ad5de61b370b80e091d06f2a44bc382f420f643e0665c39309b73cde0fda8a1
Tx prefix hash: 2e685786668feef51c6b8efd5add699319ea51e1d3427bff3e3c4996ee530ad2
Tx public key: 2b643caf9bed2fb6f85d6182d8d8040ee3e0e20bb094bdea507b9da219a3a15b
| Timestamp: 1780988097 | Timestamp [UTC]: 2026-06-09 06:54:57 | Age [y:d:h:m:s]: 00:000:07:53:58 |
| Block: 8180 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 475 | RingCT/type: yes/0 |
| Extra: 012b643caf9bed2fb6f85d6182d8d8040ee3e0e20bb094bdea507b9da219a3a15b020900000001e49593ff00 | ||
1 output(s) for total of 34.639747344821 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5587a08eba0308b23c3d1a033762eaaef7e0ea3da4b49fc60c59e9fc2deb448f | 34.639747344821 | 10128 of 0 | <ae> |
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": 8240,
"vin": [ {
"gen": {
"height": 8180
}
}
],
"vout": [ {
"amount": 34639747344821,
"target": {
"tagged_key": {
"key": "5587a08eba0308b23c3d1a033762eaaef7e0ea3da4b49fc60c59e9fc2deb448f",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 43, 100, 60, 175, 155, 237, 47, 182, 248, 93, 97, 130, 216, 216, 4, 14, 227, 224, 226, 11, 176, 148, 189, 234, 80, 123, 157, 162, 25, 163, 161, 91, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}