← previous blocknext block →recent activity
Analyzing
Block #106,550,408
23 transactions · 23 stateful · 2026-09-20 19:47:12 UTC
Parallelism
57/100
Blocked
57%
Avg conflicts / tx
1.74
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,550,408 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w311w212w313w314w416w517w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e9b4cfc…4a39
0x34b655…2a6f
16 touches
28 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x0a6cb118…4ca8
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0x5e9b4cfc2e…294a39
Audit this contract →
← previous block·next block →recent activity