← previous blocknext block →recent activity
Analyzing
Block #99,988,613
20 transactions · 17 stateful · 2026-08-28 20:03:03 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,988,613 · 20 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
1w04w09w110w211w312w414w515w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x627738d1…db02
0x34b655…2a6f
8 touches
6 conflicts
0x83f3d320…fb59
0x34b655…2a6f
8 touches
6 conflicts
0xd039b7ef…b56d
0x34b655…2a6f
8 touches
6 conflicts
0xfc1d1594…b59f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9eef1610…1564
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x627738d150…b6db02
Audit this contract →
← previous block·next block →recent activity