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: c666c51402c58d49ebc28de51b89facb62d23bbf097dc435940e689ec81e77f4
Tx prefix hash: ca2061c70d63e544ade2dbe9552f1fb6a7cd70e2f48061cf72f71d235dbb054c
Tx public key: 173b9d67e674bef157d132b32d616fe896211ae9eee9a73ed8a5802e1d7baa54
| Timestamp: 1780717135 | Timestamp [UTC]: 2026-06-06 03:38:55 | Age [y:d:h:m:s]: 00:007:07:23:21 |
| Block: 6208 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2537 | RingCT/type: yes/0 |
| Extra: 01173b9d67e674bef157d132b32d616fe896211ae9eee9a73ed8a5802e1d7baa54020900000005e49593ff00 | ||
1 output(s) for total of 34.770282994115 HMNY
| stealth address | amount | amount idx | tag |
| 00: 59f6e769b1aab8c5fdd510a34e99a87ad6b1a2aa1ab36fc2f54e28d804f397b3 | 34.770282994115 | 7687 of 0 | <40> |
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": 6268,
"vin": [ {
"gen": {
"height": 6208
}
}
],
"vout": [ {
"amount": 34770282994115,
"target": {
"tagged_key": {
"key": "59f6e769b1aab8c5fdd510a34e99a87ad6b1a2aa1ab36fc2f54e28d804f397b3",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 23, 59, 157, 103, 230, 116, 190, 241, 87, 209, 50, 179, 45, 97, 111, 232, 150, 33, 26, 233, 238, 233, 167, 62, 216, 165, 128, 46, 29, 123, 170, 84, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}