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: 5a63101c1cbd90e910ff8ef28646c4c721e5f884248b15aa540ea08ade4737fe
Tx prefix hash: faf329343dacc75e261817336d3d6325f33418f7a3c7e840028a4f472c893ed8
Tx public key: 149289ddab03fe3dc3e610124d0da765b27fd24e41d3188e7bcb5cf1f2ab79c2
| Timestamp: 1780687478 | Timestamp [UTC]: 2026-06-05 19:24:38 | Age [y:d:h:m:s]: 00:003:06:11:19 |
| Block: 5482 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2404 | RingCT/type: yes/0 |
| Extra: 01149289ddab03fe3dc3e610124d0da765b27fd24e41d3188e7bcb5cf1f2ab79c2020900000001e49593ff00 | ||
1 output(s) for total of 34.818464022903 HMNY
| stealth address | amount | amount idx | tag |
| 00: 152195685dcab78696423f415f46d60523ae9b27f83483fd916ccd9cafc7cf96 | 34.818464022903 | 6921 of 0 | <4b> |
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": 5542,
"vin": [ {
"gen": {
"height": 5482
}
}
],
"vout": [ {
"amount": 34818464022903,
"target": {
"tagged_key": {
"key": "152195685dcab78696423f415f46d60523ae9b27f83483fd916ccd9cafc7cf96",
"view_tag": "4b"
}
}
}
],
"extra": [ 1, 20, 146, 137, 221, 171, 3, 254, 61, 195, 230, 16, 18, 77, 13, 167, 101, 178, 127, 210, 78, 65, 211, 24, 142, 123, 203, 92, 241, 242, 171, 121, 194, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}