← previous blocknext block →recent activity
Analyzing
Block #84,118,316
29 transactions · 23 stateful · 2026-06-27 22:02:24 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,118,316 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w311w013w014w115w117w420w021w123w226w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x81f33f24…785e
0xd32edf…ff58
5 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe3a0d266…1922
0x34b655…2a6f
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
10 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity