← previous blocknext block →recent activity
Analyzing
Block #98,607,250
10 transactions · 9 stateful · 2026-08-23 23:34:39 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,607,250 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
4 touches
1 conflict
0xc1a3e281…c954
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x090e1599…b965
0x34b655…2a6f
2 touches
0 conflicts
0x14f3db86…c03e
0x34b655…2a6f
2 touches
0 conflicts
0x58658217…80ff
0x34b655…2a6f
2 touches
0 conflicts
0x7401eb95…986b
0x34b655…2a6f
2 touches
0 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: Perpl
3 conflicts on slot 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity