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: ef43860188c74ab0276dc1008966fdba3099effb71e20392343402df0a97f908
Tx prefix hash: fe466a11d8fd53fc5a5af0a4a18a472ef48e635c41a90a717f1828a6c92452f3
Tx public key: bc98d44b57b01775c3cd942a4f1605d76a1b3bf33fd215ae1513b3408e563555
| Timestamp: 1779874154 | Timestamp [UTC]: 2026-05-27 09:29:14 | Age [y:d:h:m:s]: 00:012:16:06:43 |
| Block: 2856 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5030 | RingCT/type: yes/0 |
| Extra: 01bc98d44b57b01775c3cd942a4f1605d76a1b3bf33fd215ae1513b3408e56355502090000000126697be300 | ||
1 output(s) for total of 34.993296820478 HMNY
| stealth address | amount | amount idx | tag |
| 00: 760f171d6daad764da3bacf44fb1bbbb9e661c024ad7bc9f541e59cd7894851f | 34.993296820478 | 3382 of 0 | <77> |
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": 2916,
"vin": [ {
"gen": {
"height": 2856
}
}
],
"vout": [ {
"amount": 34993296820478,
"target": {
"tagged_key": {
"key": "760f171d6daad764da3bacf44fb1bbbb9e661c024ad7bc9f541e59cd7894851f",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 188, 152, 212, 75, 87, 176, 23, 117, 195, 205, 148, 42, 79, 22, 5, 215, 106, 27, 59, 243, 63, 210, 21, 174, 21, 19, 179, 64, 142, 86, 53, 85, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}