← previous blocknext block →recent activity
Analyzing
Block #106,372,386
21 transactions · 18 stateful · 2026-09-20 04:51:12 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,372,386 · 21 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
1w02w13w24w35w07w08w110w211w212w415w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf228c4…c2e3
0x34b655…2a6f
8 touches
6 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0x9c2fc330…0091
0x34b655…2a6f
6 touches
3 conflicts
0xae5581cb…10ed
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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
6 conflicts on slot 0x8bf228c4d2…18c2e3
Audit this contract →
← previous block·next block →recent activity