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: 8fa907c2560e54fafcbfc4d920c7fc3028f869d9fcc74e31019726a2907894eb
Tx prefix hash: 1ff1d931a345954777be4487c757eb35a5ccf6808c812b7d993a3c1cf60210df
Tx public key: 47838ee523d748c1ffe95a6c3ba846e450eedb341a4c4c334e41908b73251027
| Timestamp: 1779885112 | Timestamp [UTC]: 2026-05-27 12:31:52 | Age [y:d:h:m:s]: 00:012:12:14:55 |
| Block: 3003 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4883 | RingCT/type: yes/0 |
| Extra: 0147838ee523d748c1ffe95a6c3ba846e450eedb341a4c4c334e41908b7325102702090000000426697be300 | ||
1 output(s) for total of 34.983486757184 HMNY
| stealth address | amount | amount idx | tag |
| 00: de7d9cbfeaedbb04ec56bf55462de120b1d7cb5a2f8196b21a0ac6b9ffac1b21 | 34.983486757184 | 3565 of 0 | <6d> |
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": 3063,
"vin": [ {
"gen": {
"height": 3003
}
}
],
"vout": [ {
"amount": 34983486757184,
"target": {
"tagged_key": {
"key": "de7d9cbfeaedbb04ec56bf55462de120b1d7cb5a2f8196b21a0ac6b9ffac1b21",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 71, 131, 142, 229, 35, 215, 72, 193, 255, 233, 90, 108, 59, 168, 70, 228, 80, 238, 219, 52, 26, 76, 76, 51, 78, 65, 144, 139, 115, 37, 16, 39, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}