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: 75609ad5e457ede3aef466c8126081357437272d4a7452717f2ca0734fd8c5b7
Tx prefix hash: 780cc10083e331dc876d72a7b4e8fb33890bd8f8b034c8f9250bf425ebd94199
Tx public key: ea3241f65e2ab9f01afe5a71993704ac53a2370976833903ccdea0a7678f3f3c
| Timestamp: 1779916519 | Timestamp [UTC]: 2026-05-27 21:15:19 | Age [y:d:h:m:s]: 00:012:06:35:39 |
| Block: 3310 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4641 | RingCT/type: yes/0 |
| Extra: 01ea3241f65e2ab9f01afe5a71993704ac53a2370976833903ccdea0a7678f3f3c02090000000226697be300 | ||
1 output(s) for total of 34.963007942355 HMNY
| stealth address | amount | amount idx | tag |
| 00: ffeb5b7c0d08342af0ca42affb2e01f1dc707f38683b4f51134601b3952da8d5 | 34.963007942355 | 3976 of 0 | <4d> |
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": 3370,
"vin": [ {
"gen": {
"height": 3310
}
}
],
"vout": [ {
"amount": 34963007942355,
"target": {
"tagged_key": {
"key": "ffeb5b7c0d08342af0ca42affb2e01f1dc707f38683b4f51134601b3952da8d5",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 234, 50, 65, 246, 94, 42, 185, 240, 26, 254, 90, 113, 153, 55, 4, 172, 83, 162, 55, 9, 118, 131, 57, 3, 204, 222, 160, 167, 103, 143, 63, 60, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}