← previous blocknext block →recent activity
Analyzing
Block #106,235,620
42 transactions · 40 stateful · 2026-09-19 17:22:57 UTC
Parallelism
62/100
Blocked
63%
Avg conflicts / tx
2.12
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,235,620 · 42 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
1w02w13w24w35w06w414w516w527w631w832w934w1036w1037w1138w1239w1340w1441w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x94f4eab2…673c
0x34b655…2a6f
9 touches
10 conflicts
0x08f9abf1…10bf
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity