← previous blocknext block →recent activity
Analyzing
Block #106,377,348
74 transactions · 53 stateful · 2026-09-20 05:16:10 UTC
Parallelism
85/100
Blocked
57%
Avg conflicts / tx
1.39
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,377,348 · 74 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w27w39w410w520w623w129w230w337w739w840w942w1065w469w571w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x4681609f…6493
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0xf80280bc…28b6
0xd32edf…ff58
11 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xcd9ba26b…108d
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity