← previous blocknext block →recent activity
Analyzing
Block #106,389,011
30 transactions · 28 stateful · 2026-09-20 06:14:52 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,389,011 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w011w117w118w620w224w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8cb0701…3926
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x65289e13…8416
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x277f42bb…ccbf
0x34b655…2a6f
8 touches
6 conflicts
0xca92d069…9633
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
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
15 conflicts on slot 0xc8cb070152…393926
Audit this contract →
← previous block·next block →recent activity