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: e6411930da480fc501b81e6ba19b99dde938fc094bfe75447e50e325b250441a
Tx prefix hash: f730e5377032bca3360f229300aae4c79ba8d06b626cf85858675dc7f5e8f92c
Tx public key: 0d9730314b6a7ebc0c9a896e6c5bf14730ec122cf30668fff7aa414a2e18d1e8
| Timestamp: 1780826161 | Timestamp [UTC]: 2026-06-07 09:56:01 | Age [y:d:h:m:s]: 00:001:15:39:56 |
| Block: 7266 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 620 | RingCT/type: yes/0 |
| Extra: 010d9730314b6a7ebc0c9a896e6c5bf14730ec122cf30668fff7aa414a2e18d1e8020900000001e49593ff00 | ||
1 output(s) for total of 34.700188119170 HMNY
| stealth address | amount | amount idx | tag |
| 00: 94cdd160897e33db703de3b90754bb14095d74444e8179a42c308b0e53c90da4 | 34.700188119170 | 8946 of 0 | <98> |
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": 7326,
"vin": [ {
"gen": {
"height": 7266
}
}
],
"vout": [ {
"amount": 34700188119170,
"target": {
"tagged_key": {
"key": "94cdd160897e33db703de3b90754bb14095d74444e8179a42c308b0e53c90da4",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 13, 151, 48, 49, 75, 106, 126, 188, 12, 154, 137, 110, 108, 91, 241, 71, 48, 236, 18, 44, 243, 6, 104, 255, 247, 170, 65, 74, 46, 24, 209, 232, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}