← previous blocknext block →recent activity
Analyzing
Block #106,952,160
63 transactions · 51 stateful · 2026-09-22 05:30:17 UTC
Parallelism
75/100
Blocked
86%
Avg conflicts / tx
2.35
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,952,160 · 63 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
3w04w15w27w08w19w216w317w320w322w424w525w328w129w230w134w336w538w542w243w144w345w449w650w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x34a5dca8…326a
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x6c464113…4810
0x34b655…2a6f
12 touches
15 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
10 touches
10 conflicts
0xd1b40f29…9b9d
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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity