← previous blocknext block →recent activity
Analyzing
Block #96,277,758
44 transactions · 27 stateful · 2026-08-15 18:41:50 UTC
Parallelism
59/100
Blocked
78%
Avg conflicts / tx
3.14
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #96,277,758 · 44 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w511w613w719w821w926w1027w1128w1229w1330w1431w1532w1635w738w841w942w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
24 touches
66 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
24 touches
66 conflicts
0x17606ba6…1b6e
0x754704…b603
22 touches
55 conflicts
0xde7b0efb…97ee
0xd32edf…ff58
21 touches
55 conflicts
0x391d170b…bd0f
0x3bd359…433a
20 touches
45 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Uniswap: PoolManager
66 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity