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: 5e5d7181a36c9bcef0e59de01da500eae9f92c41592fde78cd84426278210d76
Tx prefix hash: 3768c0cc877a45b5f7c52b0bb6f3d4dd9fc0e0682bdeec83a39be7e3ef57ce2a
Tx public key: a8cb38c612b60a765e63e3e4f67a3e6bca6e7dec1042193f0413cf2cc9d044f6
| Timestamp: 1779805371 | Timestamp [UTC]: 2026-05-26 14:22:51 | Age [y:d:h:m:s]: 00:013:13:15:59 |
| Block: 2346 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5596 | RingCT/type: yes/0 |
| Extra: 01a8cb38c612b60a765e63e3e4f67a3e6bca6e7dec1042193f0413cf2cc9d044f602090000000526697be300 | ||
1 output(s) for total of 35.027353066933 HMNY
| stealth address | amount | amount idx | tag |
| 00: b567ff781e861567f57d874487505029c8374a05050f5964c82b25eb4fc598f0 | 35.027353066933 | 2746 of 0 | <c9> |
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": 2406,
"vin": [ {
"gen": {
"height": 2346
}
}
],
"vout": [ {
"amount": 35027353066933,
"target": {
"tagged_key": {
"key": "b567ff781e861567f57d874487505029c8374a05050f5964c82b25eb4fc598f0",
"view_tag": "c9"
}
}
}
],
"extra": [ 1, 168, 203, 56, 198, 18, 182, 10, 118, 94, 99, 227, 228, 246, 122, 62, 107, 202, 110, 125, 236, 16, 66, 25, 63, 4, 19, 207, 44, 201, 208, 68, 246, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}