← previous blocknext block →recent activity
Analyzing
Block #106,566,366
46 transactions · 42 stateful · 2026-09-20 21:07:30 UTC
Parallelism
72/100
Blocked
64%
Avg conflicts / tx
2.54
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,566,366 · 46 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w39w410w511w612w713w819w220w229w230w332w433w939w540w641w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x110a3804…f842
0x34b655…2a6f
26 touches
78 conflicts
0x609cd3fd…3db5
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
12 touches
15 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
12 touches
15 conflicts
0x824706a6…e8f2
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xcc8faac2…c766
0x065c9d…c394
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
78 conflicts on slot 0x110a380404…49f842
Audit this contract →
← previous block·next block →recent activity