← previous blocknext block →recent activity
Analyzing
Block #106,414,594
19 transactions · 18 stateful · 2026-09-20 08:23:37 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,414,594 · 19 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
1w02w13w14w26w07w08w39w111w212w313w414w517w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x31e47e6c…87f9
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x3cff90b9…3827
0x34b655…2a6f
8 touches
6 conflicts
0xe0debfa5…c63e
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
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 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity