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: 71e8550748d73216d6f33edcd31fae007c42a1319371a595534578d8dfc27a8d
Tx prefix hash: 5f0e4f08b120a0b6c44e3b294e9b5035ac8df22c9a27097dce3cad6d31da0e0f
Tx public key: f648961a7969ab8edddce4e581aa479d7dd2e6265baacb948c1e077d1522e6bc
| Timestamp: 1780804945 | Timestamp [UTC]: 2026-06-07 04:02:25 | Age [y:d:h:m:s]: 00:001:19:16:28 |
| Block: 6926 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 960 | RingCT/type: yes/0 |
| Extra: 01f648961a7969ab8edddce4e581aa479d7dd2e6265baacb948c1e077d1522e6bc020900000001e49593ff00 | ||
1 output(s) for total of 34.722698459975 HMNY
| stealth address | amount | amount idx | tag |
| 00: 59d9047988301ae682fb6e81e7029c34dd9d4ee0225594a7a2e267ff956c0bd5 | 34.722698459975 | 8544 of 0 | <8f> |
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": 6986,
"vin": [ {
"gen": {
"height": 6926
}
}
],
"vout": [ {
"amount": 34722698459975,
"target": {
"tagged_key": {
"key": "59d9047988301ae682fb6e81e7029c34dd9d4ee0225594a7a2e267ff956c0bd5",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 246, 72, 150, 26, 121, 105, 171, 142, 221, 220, 228, 229, 129, 170, 71, 157, 125, 210, 230, 38, 91, 170, 203, 148, 140, 30, 7, 125, 21, 34, 230, 188, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}