← previous blocknext block →recent activity
Analyzing
Block #106,109,891
51 transactions · 36 stateful · 2026-09-19 06:50:05 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
2.16
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,109,891 · 51 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w08w110w212w313w416w517w618w720w821w525w936w1038w1139w1241w1248w149w1450w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0xcfe180d7…b5a4
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x98a224e3…70e8
0x34b655…2a6f
10 touches
10 conflicts
0x96aa3e9a…62c3
0x34b655…2a6f
10 touches
10 conflicts
0x64a785e4…0110
0x34b655…2a6f
10 touches
10 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
10 touches
10 conflicts
0xe8377f79…5f5e
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
78 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity