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: 8da5db30ecc19e8f6a20b4aa110d16e3f10cef4dcd5fcf746138495a4bbfc381
Tx prefix hash: cb672d72d75d11f6ef056ae55e78bd4b910d17bf20045449c3912d53dd0e7f0b
Tx public key: d05f858ef2bb30611c2adf88cb9cf744ef7df7e6f63bba86ec7f9464e8f2b266
| Timestamp: 1779882353 | Timestamp [UTC]: 2026-05-27 11:45:53 | Age [y:d:h:m:s]: 00:020:20:36:26 |
| Block: 2962 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5783 | RingCT/type: yes/0 |
| Extra: 01d05f858ef2bb30611c2adf88cb9cf744ef7df7e6f63bba86ec7f9464e8f2b26602090000000126697be300 | ||
1 output(s) for total of 34.986222620697 HMNY
| stealth address | amount | amount idx | tag |
| 00: 850780f8889ddc196893aba6654bbd96cf72a265256bbf26061fe7ee9acd3136 | 34.986222620697 | 3514 of 0 | <93> |
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": 3022,
"vin": [ {
"gen": {
"height": 2962
}
}
],
"vout": [ {
"amount": 34986222620697,
"target": {
"tagged_key": {
"key": "850780f8889ddc196893aba6654bbd96cf72a265256bbf26061fe7ee9acd3136",
"view_tag": "93"
}
}
}
],
"extra": [ 1, 208, 95, 133, 142, 242, 187, 48, 97, 28, 42, 223, 136, 203, 156, 247, 68, 239, 125, 247, 230, 246, 59, 186, 134, 236, 127, 148, 100, 232, 242, 178, 102, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}