← previous blocknext block →recent activity
Analyzing
Block #106,569,027
41 transactions · 33 stateful · 2026-09-20 21:20:54 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
2.32
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,569,027 · 41 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
1w03w17w08w29w010w111w212w013w114w216w317w418w523w627w728w829w930w1032w1133w1234w1335w1436w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
26 touches
78 conflicts
0x20b1228b…2487
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0x2589c92d…04fe
0x34b655…2a6f
10 touches
10 conflicts
0x5906754f…b584
0x34b655…2a6f
8 touches
6 conflicts
0x71a05713…b3ce
0x34b655…2a6f
8 touches
6 conflicts
0x4089d428…b018
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
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
78 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity