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: efd25a549018c070b233a155f941ad2b9607815bd3c75f86d0cc2dbf023262cb
Tx prefix hash: ee76e19344a991064f6f5988fb473d55e59541fd8566e33edd6c51966dbc5391
Tx public key: 9a3efea6dad685257a7e13344025afe67f17d579cb028bf517dad21f20978edd
| Timestamp: 1780685418 | Timestamp [UTC]: 2026-06-05 18:50:18 | Age [y:d:h:m:s]: 00:003:05:56:29 |
| Block: 5386 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2500 | RingCT/type: yes/0 |
| Extra: 019a3efea6dad685257a7e13344025afe67f17d579cb028bf517dad21f20978edd020900000001e49593ff00 | ||
1 output(s) for total of 34.824840063886 HMNY
| stealth address | amount | amount idx | tag |
| 00: 393ffa35cf86bbcb9dd9b96e2a9a2901c20d242d8a6b1497a8aa4e5bc115b0c5 | 34.824840063886 | 6823 of 0 | <0a> |
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": 5446,
"vin": [ {
"gen": {
"height": 5386
}
}
],
"vout": [ {
"amount": 34824840063886,
"target": {
"tagged_key": {
"key": "393ffa35cf86bbcb9dd9b96e2a9a2901c20d242d8a6b1497a8aa4e5bc115b0c5",
"view_tag": "0a"
}
}
}
],
"extra": [ 1, 154, 62, 254, 166, 218, 214, 133, 37, 122, 126, 19, 52, 64, 37, 175, 230, 127, 23, 213, 121, 203, 2, 139, 245, 23, 218, 210, 31, 32, 151, 142, 221, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}