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: 40fc46a62b7ccfbdcd30abeb36ff0307c8362a17d2648dd9ba651bffa3ae7c3f
Tx prefix hash: 26b94122e8ecf1dd6f26be87d65cfc81e72f8f77d1086f409430f7f54376559e
Tx public key: bd4f7978a3ec0fbf3f865b96356d686939f56b476f8eb259d528dc4acb2c18a7
| Timestamp: 1779717762 | Timestamp [UTC]: 2026-05-25 14:02:42 | Age [y:d:h:m:s]: 00:014:09:16:11 |
| Block: 1692 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6194 | RingCT/type: yes/0 |
| Extra: 01bd4f7978a3ec0fbf3f865b96356d686939f56b476f8eb259d528dc4acb2c18a7020900000003ba6d17be00 | ||
1 output(s) for total of 35.071073702236 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2e95458f8b7f0b3f11f28449151d022bfd0bcc49a9393bdabe2e9a05519e606 | 35.071073702236 | 1861 of 0 | <fc> |
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": 1752,
"vin": [ {
"gen": {
"height": 1692
}
}
],
"vout": [ {
"amount": 35071073702236,
"target": {
"tagged_key": {
"key": "c2e95458f8b7f0b3f11f28449151d022bfd0bcc49a9393bdabe2e9a05519e606",
"view_tag": "fc"
}
}
}
],
"extra": [ 1, 189, 79, 121, 120, 163, 236, 15, 191, 63, 134, 91, 150, 53, 109, 104, 105, 57, 245, 107, 71, 111, 142, 178, 89, 213, 40, 220, 74, 203, 44, 24, 167, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}