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: 1c7e058ef126768ae584c03b5f046ea2ff8c1d918b5f95478a70c0c94325453f
Tx prefix hash: 43e4841baccef131e23d5beef68d3e7c566858eacbc0042c5cdb3818d344ff4f
Tx public key: cb3fc87ae5ad74f22587c919a1df7c6f0b70a7a1d87d771623ea35c78129f992
| Timestamp: 1779972226 | Timestamp [UTC]: 2026-05-28 12:43:46 | Age [y:d:h:m:s]: 00:011:14:06:02 |
| Block: 3857 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4043 | RingCT/type: yes/0 |
| Extra: 01cb3fc87ae5ad74f22587c919a1df7c6f0b70a7a1d87d771623ea35c78129f99202090000000226697be300 | ||
1 output(s) for total of 34.926549334852 HMNY
| stealth address | amount | amount idx | tag |
| 00: 07ead69318e92dd14df6c8449e8243fc14378accbb30765f34355803437cddbc | 34.926549334852 | 4712 of 0 | <8c> |
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": 3917,
"vin": [ {
"gen": {
"height": 3857
}
}
],
"vout": [ {
"amount": 34926549334852,
"target": {
"tagged_key": {
"key": "07ead69318e92dd14df6c8449e8243fc14378accbb30765f34355803437cddbc",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 203, 63, 200, 122, 229, 173, 116, 242, 37, 135, 201, 25, 161, 223, 124, 111, 11, 112, 167, 161, 216, 125, 119, 22, 35, 234, 53, 199, 129, 41, 249, 146, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}