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: 4ccfc52bea3d9390ee2c3d5522a433b74e30ea1faf9c344dbdc643924979d726
Tx prefix hash: c6ae8116437c83e30cee72455acebbbfdc93f1ae4f3b2c5b80e1305b255d3a9c
Tx public key: 81c279c2ef9ee2a0a1b5a5a692b94b8a6e4c562cf7b6bc057d1b65ce23f7e660
| Timestamp: 1779980459 | Timestamp [UTC]: 2026-05-28 15:00:59 | Age [y:d:h:m:s]: 00:019:18:14:07 |
| Block: 3915 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4830 | RingCT/type: yes/0 |
| Extra: 0181c279c2ef9ee2a0a1b5a5a692b94b8a6e4c562cf7b6bc057d1b65ce23f7e66002090000000226697be300 | ||
1 output(s) for total of 34.951692152722 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09cdc9fd91ec49a04298629eaa5fa1f68dd786c437ae46feeb4206542aae8ef9 | 34.951692152722 | 4805 of 0 | <da> |
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": 3975,
"vin": [ {
"gen": {
"height": 3915
}
}
],
"vout": [ {
"amount": 34951692152722,
"target": {
"tagged_key": {
"key": "09cdc9fd91ec49a04298629eaa5fa1f68dd786c437ae46feeb4206542aae8ef9",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 129, 194, 121, 194, 239, 158, 226, 160, 161, 181, 165, 166, 146, 185, 75, 138, 110, 76, 86, 44, 247, 182, 188, 5, 125, 27, 101, 206, 35, 247, 230, 96, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}