← previous blocknext block →recent activity
Analyzing
Block #106,570,308
18 transactions · 15 stateful · 2026-09-20 21:27:21 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,570,308 · 18 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
1w02w13w14w210w012w114w215w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0x6dcc4bf3…eb84
0x34b655…2a6f
8 touches
6 conflicts
0x6f1f2dbc…e859
0x34b655…2a6f
8 touches
6 conflicts
0x7c925651…2372
0x34b655…2a6f
8 touches
6 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity