← previous blocknext block →recent activity
Analyzing
Block #98,766,333
24 transactions · 17 stateful · 2026-08-24 13:10:50 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,766,333 · 24 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
2w08w010w111w214w315w016w417w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x729c91b8…9538
0x188d58…ea8e
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x729c91b8…9537
0x188d58…ea8e
8 touches
6 conflicts
0xfe3d7939…8312
0x065c9d…c394
7 touches
6 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
6 touches
3 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
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 0x729c91b8a3…e19538
Audit this contract →
← previous block·next block →recent activity