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: 7d15b1b66810161677e41e846fcfddce23c7b57cfaee52ab0fba02b30f68a8f5
Tx prefix hash: eaf29d436009af55cdb23a3c9fb18e63232bbc03a26911dab5414b9a1a75f830
Tx public key: 27509f7bf4f7547005c6ab3a59ab2e8180e3874e2889e85b784eb893fec6fd12
| Timestamp: 1779977451 | Timestamp [UTC]: 2026-05-28 14:10:51 | Age [y:d:h:m:s]: 00:011:11:25:06 |
| Block: 3898 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3988 | RingCT/type: yes/0 |
| Extra: 0127509f7bf4f7547005c6ab3a59ab2e8180e3874e2889e85b784eb893fec6fd1202090000000526697be300 | ||
1 output(s) for total of 34.923818137689 HMNY
| stealth address | amount | amount idx | tag |
| 00: df6dbf475d9975eb7a7cd2acfe5893c373a2f1d257ab8211bfaa648dd339d7d4 | 34.923818137689 | 4776 of 0 | <31> |
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": 3958,
"vin": [ {
"gen": {
"height": 3898
}
}
],
"vout": [ {
"amount": 34923818137689,
"target": {
"tagged_key": {
"key": "df6dbf475d9975eb7a7cd2acfe5893c373a2f1d257ab8211bfaa648dd339d7d4",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 39, 80, 159, 123, 244, 247, 84, 112, 5, 198, 171, 58, 89, 171, 46, 129, 128, 227, 135, 78, 40, 137, 232, 91, 120, 78, 184, 147, 254, 198, 253, 18, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}