← previous blocknext block →recent activity
Analyzing
Block #99,875,941
24 transactions · 23 stateful · 2026-08-28 10:35:16 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,875,941 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w09w011w112w113w214w315w419w120w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xf9dee05b…b4fa
0x34b655…2a6f
8 touches
6 conflicts
0x5a3732cb…edac
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x2d20b59b…b4ea
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: Perpl
10 conflicts on slot 0x886db2649c…07846e
Audit this contract →
← previous block·next block →recent activity