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: b420e1f760760d50d3686bbc8509d88116f2c34cd3e3c45ecfa4260d01176cf1
Tx prefix hash: fd717a25bcf6322f13e488d4b2ef3bc04e5f4fadf549506ce5d9812784c8945e
Tx public key: 2113a828a7fd745a3f69d1e7ca832a6fc38587a1d69adf5396f6cf5b397d89b4
| Timestamp: 1780691620 | Timestamp [UTC]: 2026-06-05 20:33:40 | Age [y:d:h:m:s]: 00:003:05:02:17 |
| Block: 5742 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2144 | RingCT/type: yes/0 |
| Extra: 012113a828a7fd745a3f69d1e7ca832a6fc38587a1d69adf5396f6cf5b397d89b4020900000001e49593ff00 | ||
1 output(s) for total of 34.801201440208 HMNY
| stealth address | amount | amount idx | tag |
| 00: 37c1fd676c8a5970106ebc0c57871d71b7d9c535502ff91f417d670eaa9d704b | 34.801201440208 | 7195 of 0 | <ea> |
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": 5802,
"vin": [ {
"gen": {
"height": 5742
}
}
],
"vout": [ {
"amount": 34801201440208,
"target": {
"tagged_key": {
"key": "37c1fd676c8a5970106ebc0c57871d71b7d9c535502ff91f417d670eaa9d704b",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 33, 19, 168, 40, 167, 253, 116, 90, 63, 105, 209, 231, 202, 131, 42, 111, 195, 133, 135, 161, 214, 154, 223, 83, 150, 246, 207, 91, 57, 125, 137, 180, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}