← previous blocknext block →recent activity
Analyzing
Block #100,612,486
26 transactions · 20 stateful · 2026-08-31 00:26:30 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,612,486 · 26 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
1w03w16w07w18w29w116w317w419w022w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a567
0x188d58…ea8e
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x46cb45de…a566
0x188d58…ea8e
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x09beabbc…065d
0x188d58…ea8e
6 touches
3 conflicts
0x09beabbc…065c
0x188d58…ea8e
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 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
6 conflicts on slot 0x46cb45de01…66a567
Audit this contract →
← previous block·next block →recent activity