← previous blocknext block →recent activity
Analyzing
Block #98,926,223
36 transactions · 30 stateful · 2026-08-25 02:35:26 UTC
Parallelism
86/100
Blocked
47%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,926,223 · 36 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
2w03w07w08w110w111w212w213w114w015w016w217w119w123w224w325w326w431w335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e017
0x188d58…ea8e
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
8 touches
6 conflicts
0x8bcefba2…8cc8
0x065c9d…c394
7 touches
6 conflicts
0x9ba7d0c8…ec52
0xee8c0e…1242
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 0x00f7e3b74f…eee017
Audit this contract →
← previous block·next block →recent activity