← previous blocknext block →recent activity
Analyzing
Block #110,375,642
30 transactions · 24 stateful · 2026-10-04 04:51:32 UTC
Parallelism
87/100
Blocked
25%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,375,642 · 30 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
1w04w05w16w17w210w224w326w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e015
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…004f
0x80c745…7210
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x00f7e3b7…e017
0x188d58…ea8e
4 touches
1 conflict
0x46b0275d…23df
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0xd02cf112…a823
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x00f7e3b74f…eee015
Audit this contract →
← previous block·next block →recent activity