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: 0e6cafb3e0fbe1999210ec2b5110e8f3be1399c97a660b6f209f2a8e572115aa
Tx prefix hash: ee5832a29df34fe90d59f7a65fcac1048d881b01aca8aebeb82bbd903b29451e
Tx public key: 718161d9e67ad839cee62ec19686c82a4d105d40ce79f4bdfeff115f5a872099
| Timestamp: 1780080340 | Timestamp [UTC]: 2026-05-29 18:45:40 | Age [y:d:h:m:s]: 00:010:04:33:13 |
| Block: 4759 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3127 | RingCT/type: yes/0 |
| Extra: 01718161d9e67ad839cee62ec19686c82a4d105d40ce79f4bdfeff115f5a87209902090000000126697be300 | ||
1 output(s) for total of 34.866512307387 HMNY
| stealth address | amount | amount idx | tag |
| 00: b5f6696373e7aa25e6d16aafa22dbff2b430a0991531a96777a5b3e2a34f172f | 34.866512307387 | 5980 of 0 | <ce> |
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": 4819,
"vin": [ {
"gen": {
"height": 4759
}
}
],
"vout": [ {
"amount": 34866512307387,
"target": {
"tagged_key": {
"key": "b5f6696373e7aa25e6d16aafa22dbff2b430a0991531a96777a5b3e2a34f172f",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 113, 129, 97, 217, 230, 122, 216, 57, 206, 230, 46, 193, 150, 134, 200, 42, 77, 16, 93, 64, 206, 121, 244, 189, 254, 255, 17, 95, 90, 135, 32, 153, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}