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: c1cc2e25a353c16604634c40567091f4e9238fe33c654a45e86a388e02995180
Tx prefix hash: 22682e7b42da1d2a38ffcd55e01fe6f0c57047a03394c605d0430e930d1084cc
Tx public key: bef2367b968d126e9f8981ca231e852d03db14f4ffaf9903142799da5c34d481
| Timestamp: 1780720850 | Timestamp [UTC]: 2026-06-06 04:40:50 | Age [y:d:h:m:s]: 00:002:20:55:07 |
| Block: 6244 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1642 | RingCT/type: yes/0 |
| Extra: 01bef2367b968d126e9f8981ca231e852d03db14f4ffaf9903142799da5c34d481020900000002e49593ff00 | ||
1 output(s) for total of 34.767895587942 HMNY
| stealth address | amount | amount idx | tag |
| 00: df047a4f80ef3c3346652b7226632f64aadc66d71b89eb73491c190f2f002a01 | 34.767895587942 | 7725 of 0 | <dd> |
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": 6304,
"vin": [ {
"gen": {
"height": 6244
}
}
],
"vout": [ {
"amount": 34767895587942,
"target": {
"tagged_key": {
"key": "df047a4f80ef3c3346652b7226632f64aadc66d71b89eb73491c190f2f002a01",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 190, 242, 54, 123, 150, 141, 18, 110, 159, 137, 129, 202, 35, 30, 133, 45, 3, 219, 20, 244, 255, 175, 153, 3, 20, 39, 153, 218, 92, 52, 212, 129, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}