← previous blocknext block →recent activity
Analyzing
Block #100,607,700
19 transactions · 17 stateful · 2026-08-31 00:02:26 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,607,700 · 19 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
2w03w15w06w07w18w211w313w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a566
0x188d58…ea8e
10 touches
10 conflicts
0x46cb45de…a568
0x188d58…ea8e
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xd8be3a1f…b5aa
0x065c9d…c394
7 touches
6 conflicts
0x846f2172…fd54
0x0555e3…2b9c
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
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 0x46cb45de01…66a566
Audit this contract →
← previous block·next block →recent activity