← previous blocknext block →recent activity
Analyzing
Block #87,922,361
22 transactions · 21 stateful · 2026-07-15 13:16:40 UTC
Parallelism
82/100
Blocked
52%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,922,361 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w26w29w010w111w012w114w115w216w317w018w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x729c91b8…9537
0x188d58…ea8e
6 touches
3 conflicts
0x729c91b8…9538
0x188d58…ea8e
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x8c3646f6…357d
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x91220b8f…7a02
0x1b6862…e19c
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
3 conflicts on slot 0x729c91b8a3…e19537
Audit this contract →
← previous block·next block →recent activity