← previous blocknext block →recent activity
Analyzing
Block #106,223,900
40 transactions · 38 stateful · 2026-09-19 16:23:55 UTC
Parallelism
77/100
Blocked
58%
Avg conflicts / tx
1.75
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,223,900 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w28w29w310w411w517w221w623w725w527w628w739w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3b84582…0ade
0x34b655…2a6f
16 touches
28 conflicts
0x94ed2e6a…c6b6
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x53103bb4…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
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
28 conflicts on slot 0xd3b8458246…f30ade
Audit this contract →
← previous block·next block →recent activity