← previous blocknext block →recent activity
Analyzing
Block #106,373,450
30 transactions · 30 stateful · 2026-09-20 04:56:34 UTC
Parallelism
47/100
Blocked
67%
Avg conflicts / tx
4.1
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,373,450 · 30 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w29w110w211w313w414w515w516w617w718w820w1021w1122w1223w1325w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9b7b017…84e5
0x34b655…2a6f
28 touches
91 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
26 touches
78 conflicts
0x464e3025…0596
0x34b655…2a6f
18 touches
36 conflicts
0xac0b4a08…faae
0x34b655…2a6f
12 touches
15 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0xc9b7b017a1…8f84e5
Audit this contract →
← previous block·next block →recent activity