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: ba704566d3c8da92591e4e63c7cd5bbaa1e23e7975e3b7f97aca926c967b2ccd
Tx prefix hash: 8dbac5bb37d2fa9dff55e3df93da41be12c8feaefb6be801a749820308289575
Tx public key: 5366a008535517ecc28b5cf113cc68dc15b2adcc4f3897805f825d7c70c708f0
| Timestamp: 1780691522 | Timestamp [UTC]: 2026-06-05 20:32:02 | Age [y:d:h:m:s]: 00:003:04:14:45 |
| Block: 5733 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2153 | RingCT/type: yes/0 |
| Extra: 015366a008535517ecc28b5cf113cc68dc15b2adcc4f3897805f825d7c70c708f0020900000001e49593ff00 | ||
1 output(s) for total of 34.801798848122 HMNY
| stealth address | amount | amount idx | tag |
| 00: 31c87b0369513f6f6df9e46de94790a16ffb56f689283d4fac866772b478f080 | 34.801798848122 | 7186 of 0 | <8f> |
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": 5793,
"vin": [ {
"gen": {
"height": 5733
}
}
],
"vout": [ {
"amount": 34801798848122,
"target": {
"tagged_key": {
"key": "31c87b0369513f6f6df9e46de94790a16ffb56f689283d4fac866772b478f080",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 83, 102, 160, 8, 83, 85, 23, 236, 194, 139, 92, 241, 19, 204, 104, 220, 21, 178, 173, 204, 79, 56, 151, 128, 95, 130, 93, 124, 112, 199, 8, 240, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}