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: 7e574bc5a4ea57aa14e6a603d521f79e5deb7ccc61ce52c43123d96c9917ed6b
Tx prefix hash: 5cc4446b3761b7519f42ef7b5eff549113767f3bc194577cd99e9a2e427812f2
Tx public key: 67652fda8979c57c20c6f740f5c82ef2d841a4f2a1f055d57626e6c18c771812
| Timestamp: 1780764472 | Timestamp [UTC]: 2026-06-06 16:47:52 | Age [y:d:h:m:s]: 00:002:07:58:55 |
| Block: 6604 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1282 | RingCT/type: yes/0 |
| Extra: 0167652fda8979c57c20c6f740f5c82ef2d841a4f2a1f055d57626e6c18c771812020900000002e49593ff00 | ||
1 output(s) for total of 34.744030540213 HMNY
| stealth address | amount | amount idx | tag |
| 00: d6b3433a084e685c42758acb4c8234bde422c5ce0fec061d097b732137d0b364 | 34.744030540213 | 8136 of 0 | <7d> |
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": 6664,
"vin": [ {
"gen": {
"height": 6604
}
}
],
"vout": [ {
"amount": 34744030540213,
"target": {
"tagged_key": {
"key": "d6b3433a084e685c42758acb4c8234bde422c5ce0fec061d097b732137d0b364",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 103, 101, 47, 218, 137, 121, 197, 124, 32, 198, 247, 64, 245, 200, 46, 242, 216, 65, 164, 242, 161, 240, 85, 213, 118, 38, 230, 193, 140, 119, 24, 18, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}