← previous blocknext block →recent activity
Analyzing
Block #100,462,492
17 transactions · 16 stateful · 2026-08-30 11:51:56 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,462,492 · 17 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
1w03w14w08w29w010w312w113w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a568
0x188d58…ea8e
8 touches
6 conflicts
0x46cb45de…a566
0x188d58…ea8e
8 touches
6 conflicts
0x846f2172…fd54
0x0555e3…2b9c
8 touches
6 conflicts
0xf9da5665…2703
0x754704…b603
6 touches
3 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
6 touches
3 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
6 touches
3 conflicts
0x3071d008…8f8c
0x34b655…2a6f
6 touches
3 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
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…66a568
Audit this contract →
← previous block·next block →recent activity