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: 267a8c2e09445a39fbb6ce8cb84803e8b5a03b5bfd1b4239d2be4ede594b11bd
Tx prefix hash: 358e6a87c0b02b546b7e4f80bc3f86e4210193632318c4aba5e9a9523d30fcfd
Tx public key: 19ae8d73cc01d2a687ce767c7546e086e48bf1ae9799cfccd3b8eb47af2f83d2
| Timestamp: 1780120235 | Timestamp [UTC]: 2026-05-30 05:50:35 | Age [y:d:h:m:s]: 00:016:02:29:00 |
| Block: 4893 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3852 | RingCT/type: yes/0 |
| Extra: 0119ae8d73cc01d2a687ce767c7546e086e48bf1ae9799cfccd3b8eb47af2f83d202090000000426697be300 | ||
1 output(s) for total of 34.857602089922 HMNY
| stealth address | amount | amount idx | tag |
| 00: 49c2d7ea1ce21386c9629a67dbcc90d31e458462fc76933a4cb38c3973d18548 | 34.857602089922 | 6195 of 0 | <a0> |
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": 4953,
"vin": [ {
"gen": {
"height": 4893
}
}
],
"vout": [ {
"amount": 34857602089922,
"target": {
"tagged_key": {
"key": "49c2d7ea1ce21386c9629a67dbcc90d31e458462fc76933a4cb38c3973d18548",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 25, 174, 141, 115, 204, 1, 210, 166, 135, 206, 118, 124, 117, 70, 224, 134, 228, 139, 241, 174, 151, 153, 207, 204, 211, 184, 235, 71, 175, 47, 131, 210, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}