← previous blocknext block →recent activity
Analyzing
Block #99,183,879
25 transactions · 22 stateful · 2026-08-26 00:18:28 UTC
Parallelism
64/100
Blocked
59%
Avg conflicts / tx
1.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,183,879 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w08w19w210w112w313w114w415w518w619w123w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd97b0449…00a0
0x34b655…2a6f
10 touches
10 conflicts
0xee78028d…b675
0x34b655…2a6f
8 touches
6 conflicts
0x826cce18…251c
0x34b655…2a6f
6 touches
3 conflicts
0x00f245ce…1e10
0x34b655…2a6f
6 touches
3 conflicts
0x31d6dfdf…79cd
0x34b655…2a6f
6 touches
3 conflicts
0x98862f54…62ca
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
28 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity