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: d32fe3dd9e30a2cf74da0d2a512df2e9017ae9b15e4f860b325f75452f27a0d7
Tx prefix hash: 6a76fd2fa83132be9f0720ff6cac06892c65ce5999b73530b19f64b7cbe0f871
Tx public key: 60dfef7a5a7c2a25a7b4c1f652a1ae1c876f0f8db47d6fe8fec28f3acd61b40f
| Timestamp: 1781008755 | Timestamp [UTC]: 2026-06-09 12:39:15 | Age [y:d:h:m:s]: 00:008:00:05:20 |
| Block: 8574 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 171 | RingCT/type: yes/0 |
| Extra: 0160dfef7a5a7c2a25a7b4c1f652a1ae1c876f0f8db47d6fe8fec28f3acd61b40f020900000006e49593ff00 | ||
1 output(s) for total of 34.613725489434 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9e9f7ec9ff2677fe858d83522f8edc34e65a3b74f44fa37f39c9a5df93c525d | 34.613725489434 | 10590 of 0 | <3a> |
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": 8634,
"vin": [ {
"gen": {
"height": 8574
}
}
],
"vout": [ {
"amount": 34613725489434,
"target": {
"tagged_key": {
"key": "d9e9f7ec9ff2677fe858d83522f8edc34e65a3b74f44fa37f39c9a5df93c525d",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 96, 223, 239, 122, 90, 124, 42, 37, 167, 180, 193, 246, 82, 161, 174, 28, 135, 111, 15, 141, 180, 125, 111, 232, 254, 194, 143, 58, 205, 97, 180, 15, 2, 9, 0, 0, 0, 6, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}