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: dec7f6fbd587d50f005f49bd254f74e743046a8b3046b5a764a6b7af83336cb7
Tx prefix hash: 1db65024fa5cd4f74208d73c67ad9f4c624a1d430bf5f6dfb57fd5b8c0d33529
Tx public key: 559e7e91d180d1588caeb9727707e52d3a7401b34b3f1d636b441ee1a399ede4
| Timestamp: 1780822638 | Timestamp [UTC]: 2026-06-07 08:57:18 | Age [y:d:h:m:s]: 00:001:16:38:39 |
| Block: 7207 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 679 | RingCT/type: yes/0 |
| Extra: 01559e7e91d180d1588caeb9727707e52d3a7401b34b3f1d636b441ee1a399ede4020900000004e49593ff00 | ||
1 output(s) for total of 34.704093278647 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1d6d83e03bf4b40e060a8a4aae4ac7ee7bc474129bf5d08e2f57aa8181066ff8 | 34.704093278647 | 8875 of 0 | <ba> |
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": 7267,
"vin": [ {
"gen": {
"height": 7207
}
}
],
"vout": [ {
"amount": 34704093278647,
"target": {
"tagged_key": {
"key": "1d6d83e03bf4b40e060a8a4aae4ac7ee7bc474129bf5d08e2f57aa8181066ff8",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 85, 158, 126, 145, 209, 128, 209, 88, 140, 174, 185, 114, 119, 7, 229, 45, 58, 116, 1, 179, 75, 63, 29, 99, 107, 68, 30, 225, 163, 153, 237, 228, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}