← previous blocknext block →recent activity
Analyzing
Block #106,420,386
38 transactions · 35 stateful · 2026-09-20 08:52:46 UTC
Parallelism
55/100
Blocked
69%
Avg conflicts / tx
3.42
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,420,386 · 38 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
1w02w13w24w35w47w512w513w614w515w720w723w824w925w1026w1127w1228w1329w1430w1531w1636w837w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0x161db613…d254
0x34b655…2a6f
26 touches
78 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
26 touches
78 conflicts
0x80398c66…f3cc
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x3af0dd8e…0024
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
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
91 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity