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: 68a8b19d357daf7ba6b758d2fa875b78b2e0502939e269be0544593561009268
Tx prefix hash: 04c82edfb5fe3027cfaa12555fd6991cef535855d8fe8453224ad8abae11fd64
Tx public key: 5c0ec1c6c8671f5e92f622d04db6f028b422491247904114fcc99c6f61278cd1
| Timestamp: 1780982612 | Timestamp [UTC]: 2026-06-09 05:23:32 | Age [y:d:h:m:s]: 00:000:07:09:55 |
| Block: 8068 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 502 | RingCT/type: yes/0 |
| Extra: 015c0ec1c6c8671f5e92f622d04db6f028b422491247904114fcc99c6f61278cd1020900000002e49593ff00 | ||
1 output(s) for total of 34.647147990696 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6e458b0a9a2e56d246690b6ce4991cb23b98637c335d59fe35db40cc5e5a845 | 34.647147990696 | 9998 of 0 | <73> |
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": 8128,
"vin": [ {
"gen": {
"height": 8068
}
}
],
"vout": [ {
"amount": 34647147990696,
"target": {
"tagged_key": {
"key": "b6e458b0a9a2e56d246690b6ce4991cb23b98637c335d59fe35db40cc5e5a845",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 92, 14, 193, 198, 200, 103, 31, 94, 146, 246, 34, 208, 77, 182, 240, 40, 180, 34, 73, 18, 71, 144, 65, 20, 252, 201, 156, 111, 97, 39, 140, 209, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}