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: 3d45796b497d647304d96d5691d025c5430a851984f924e71dee326fd3224000
Tx prefix hash: a0631c1d2a752e436ad22ce09b26a2ffcfb34a4678539373fe8cb8023d63eacf
Tx public key: 2503be17a9cc05c6ab62326a3a987ac6e657d89b48714947d45aac684c3165b6
| Timestamp: 1780773295 | Timestamp [UTC]: 2026-06-06 19:14:55 | Age [y:d:h:m:s]: 00:002:07:34:53 |
| Block: 6683 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1217 | RingCT/type: yes/0 |
| Extra: 012503be17a9cc05c6ab62326a3a987ac6e657d89b48714947d45aac684c3165b6020900000002e49593ff00 | ||
1 output(s) for total of 34.738795680273 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4603e876a2f0d57949fdd31c3eda3374e726b618d9ee3321e3ad14057d1f6de4 | 34.738795680273 | 8243 of 0 | <e1> |
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": 6743,
"vin": [ {
"gen": {
"height": 6683
}
}
],
"vout": [ {
"amount": 34738795680273,
"target": {
"tagged_key": {
"key": "4603e876a2f0d57949fdd31c3eda3374e726b618d9ee3321e3ad14057d1f6de4",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 37, 3, 190, 23, 169, 204, 5, 198, 171, 98, 50, 106, 58, 152, 122, 198, 230, 87, 216, 155, 72, 113, 73, 71, 212, 90, 172, 104, 76, 49, 101, 182, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}