← previous blocknext block →recent activity
Analyzing
Block #74,308,222
18 transactions · 14 stateful · 2026-05-13 11:08:05 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,308,222 · 18 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
1w02w13w07w111w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x70215048…1791
0xd32edf…ff58
3 touches
1 conflict
0x5af26152…389d
0x0594c7…a3be
2 touches
0 conflicts
0xd1ffa97a…337f
0x0594c7…a3be
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 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity