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: e0eedb5977d4893efa16db00a2e76a1e431b01ebe77b5dff69dba5ddc6ce6dd4
Tx prefix hash: ed75b06bab29987f40d259a67407e2672ee918a62b4a547b60675058b6b9445f
Tx public key: 751fda149037d112b5febcf1c975252a09391fe2a2d6e34f18ec2f1949d3224d
| Timestamp: 1779965298 | Timestamp [UTC]: 2026-05-28 10:48:18 | Age [y:d:h:m:s]: 00:019:21:13:27 |
| Block: 3799 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4946 | RingCT/type: yes/0 |
| Extra: 01751fda149037d112b5febcf1c975252a09391fe2a2d6e34f18ec2f1949d3224d02090000000226697be300 | ||
1 output(s) for total of 34.935328544418 HMNY
| stealth address | amount | amount idx | tag |
| 00: e2cd61ce6263e511a4a9f794c7c6e52acddf610e276f2c0903bfde344292df05 | 34.935328544418 | 4619 of 0 | <40> |
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": 3859,
"vin": [ {
"gen": {
"height": 3799
}
}
],
"vout": [ {
"amount": 34935328544418,
"target": {
"tagged_key": {
"key": "e2cd61ce6263e511a4a9f794c7c6e52acddf610e276f2c0903bfde344292df05",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 117, 31, 218, 20, 144, 55, 209, 18, 181, 254, 188, 241, 201, 117, 37, 42, 9, 57, 31, 226, 162, 214, 227, 79, 24, 236, 47, 25, 73, 211, 34, 77, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}