← previous blocknext block →recent activity
Analyzing
Block #90,815,923
14 transactions · 14 stateful · 2026-07-27 16:10:59 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,815,923 · 14 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
1w02w13w08w09w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x729c91b8…9538
0x188d58…ea8e
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x6930727a…9bf4
0x34b655…2a6f
4 touches
1 conflict
0xd2b87a88…aa57
0x34b655…2a6f
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
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 0x729c91b8a3…e19538
Audit this contract →
← previous block·next block →recent activity