← previous blocknext block →recent activity
Analyzing
Block #88,078,004
19 transactions · 18 stateful · 2026-07-16 06:37:40 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,078,004 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbad2c6c…0d33
0x188d58…ea8e
4 touches
1 conflict
0xfbad2c6c…0d32
0x188d58…ea8e
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x33a26eb2…2df0
0x5ff137…2789
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x6e9b4ab5…a3eb
0x754704…b603
4 touches
1 conflict
0xd5b10148…e635
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0xfbad2c6c03…650d33
Audit this contract →
← previous block·next block →recent activity