← previous blocknext block →recent activity
Analyzing
Block #106,403,230
23 transactions · 22 stateful · 2026-09-20 07:26:26 UTC
Parallelism
44/100
Blocked
64%
Avg conflicts / tx
2.35
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,403,230 · 23 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
1w02w13w24w35w46w510w611w714w816w917w1019w1222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9bc5e3…f916
0x34b655…2a6f
14 touches
21 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x6d43ee99…bdd5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x482471ad…122f
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 0xcc9bc5e35b…edf916
Audit this contract →
← previous block·next block →recent activity