← previous blocknext block →recent activity
Analyzing
Block #106,188,609
22 transactions · 18 stateful · 2026-09-19 13:26:15 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,188,609 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w010w111w212w313w414w515w618w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd62f3741…b903
0x34b655…2a6f
12 touches
15 conflicts
0x58a5b9a1…5447
0x34b655…2a6f
10 touches
10 conflicts
0xe33beb97…6c6f
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
8 touches
6 conflicts
0xe5060fe3…ebe9
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
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
15 conflicts on slot 0xd62f374157…55b903
Audit this contract →
← previous block·next block →recent activity