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: 499c96228eaf5ad9dcd6d86e68d6902d69ce56d540eaff44442666243fe1919b
Tx prefix hash: 8c80e7677b3d4e57c56c80888d714d21d74d00efc738a5dbda8e71edb69b363d
Tx public key: 46e39635779dbca7a9eb8065cdac03377fe4b079867aff6e5e89afb39fca4a23
| Timestamp: 1780832038 | Timestamp [UTC]: 2026-06-07 11:33:58 | Age [y:d:h:m:s]: 00:001:09:38:09 |
| Block: 7356 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 530 | RingCT/type: yes/0 |
| Extra: 0146e39635779dbca7a9eb8065cdac03377fe4b079867aff6e5e89afb39fca4a23020900000001e49593ff00 | ||
1 output(s) for total of 34.694231942654 HMNY
| stealth address | amount | amount idx | tag |
| 00: bd447cc4abac2929932679bd9d48ae89c06e58bb131df9a41537e6b20993aced | 34.694231942654 | 9056 of 0 | <92> |
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": 7416,
"vin": [ {
"gen": {
"height": 7356
}
}
],
"vout": [ {
"amount": 34694231942654,
"target": {
"tagged_key": {
"key": "bd447cc4abac2929932679bd9d48ae89c06e58bb131df9a41537e6b20993aced",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 70, 227, 150, 53, 119, 157, 188, 167, 169, 235, 128, 101, 205, 172, 3, 55, 127, 228, 176, 121, 134, 122, 255, 110, 94, 137, 175, 179, 159, 202, 74, 35, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}