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: d0e34805bb7005cb644e1605470cdaf483366954a6719a00b889b177da120a3f
Tx prefix hash: 8200920d25d624319fce4b50aad30605c0e83988d5a3ab5f1e8222b818132d17
Tx public key: a1611b486c8022c30d987493d0db878c458a2b18412f70cb7aedeb3ff0cfc5a8
| Timestamp: 1780826258 | Timestamp [UTC]: 2026-06-07 09:57:38 | Age [y:d:h:m:s]: 00:001:15:38:19 |
| Block: 7269 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 617 | RingCT/type: yes/0 |
| Extra: 01a1611b486c8022c30d987493d0db878c458a2b18412f70cb7aedeb3ff0cfc5a8020900000001e49593ff00 | ||
1 output(s) for total of 34.699989563480 HMNY
| stealth address | amount | amount idx | tag |
| 00: d0815fd67b4d30696c780a1c90ba37bfc73a268351972681a36c0ee20620fcf9 | 34.699989563480 | 8949 of 0 | <50> |
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": 7329,
"vin": [ {
"gen": {
"height": 7269
}
}
],
"vout": [ {
"amount": 34699989563480,
"target": {
"tagged_key": {
"key": "d0815fd67b4d30696c780a1c90ba37bfc73a268351972681a36c0ee20620fcf9",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 161, 97, 27, 72, 108, 128, 34, 195, 13, 152, 116, 147, 208, 219, 135, 140, 69, 138, 43, 24, 65, 47, 112, 203, 122, 237, 235, 63, 240, 207, 197, 168, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}