← previous blocknext block →recent activity
Analyzing
Block #106,424,699
26 transactions · 24 stateful · 2026-09-20 09:14:28 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
1.88
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,424,699 · 26 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
1w02w13w24w35w411w312w315w416w517w618w619w720w821w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cd9fd28…a158
0x34b655…2a6f
14 touches
21 conflicts
0xaf717b83…4875
0x34b655…2a6f
12 touches
15 conflicts
0xd5cdf6a1…8fd6
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd5b10148…e634
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x7cd9fd286f…a7a158
Audit this contract →
← previous block·next block →recent activity