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: f1d2dca00b2869efa56c95a13177f61fcb8c40c540ed02c4e93eb7c68d1f525a
Tx prefix hash: 8d6f3f71147f873301e3f953dab5ccb47640e13af3749b36b1176a21f6c8f7eb
Tx public key: 292d87087af85441fc82d493004fdd5ab15cb11c08d96a5e80b6f678a5e1d668
| Timestamp: 1779947336 | Timestamp [UTC]: 2026-05-28 05:48:56 | Age [y:d:h:m:s]: 00:018:02:30:39 |
| Block: 3575 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5170 | RingCT/type: yes/0 |
| Extra: 01292d87087af85441fc82d493004fdd5ab15cb11c08d96a5e80b6f678a5e1d66802090000000526697be300 | ||
1 output(s) for total of 34.945340429851 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5ececcfd8779b79df552720711ef5e583e6e8a98bce6b863374df59a11153e40 | 34.945340429851 | 4316 of 0 | <d0> |
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": 3635,
"vin": [ {
"gen": {
"height": 3575
}
}
],
"vout": [ {
"amount": 34945340429851,
"target": {
"tagged_key": {
"key": "5ececcfd8779b79df552720711ef5e583e6e8a98bce6b863374df59a11153e40",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 41, 45, 135, 8, 122, 248, 84, 65, 252, 130, 212, 147, 0, 79, 221, 90, 177, 92, 177, 28, 8, 217, 106, 94, 128, 182, 246, 120, 165, 225, 214, 104, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}