← previous blocknext block →recent activity
Analyzing
Block #106,538,964
26 transactions · 22 stateful · 2026-09-20 18:49:37 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,538,964 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w114w217w318w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x629bd5e3…aeec
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0xb53e864d…e48d
0x34b655…2a6f
8 touches
6 conflicts
0xc6a8c250…737e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x629bd5e374…22aeec
Audit this contract →
← previous block·next block →recent activity