← previous blocknext block →recent activity
Analyzing
Block #106,383,617
25 transactions · 25 stateful · 2026-09-20 05:47:44 UTC
Parallelism
32/100
Blocked
80%
Avg conflicts / tx
3.8
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,383,617 · 25 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w17w210w411w513w614w715w816w917w1018w1119w1221w1322w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
22 touches
55 conflicts
0x74366c29…aa05
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x1f8a126c…9aa3
0x1b6862…e19c
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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
55 conflicts on slot 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity