← previous blocknext block →recent activity
Analyzing
Block #106,235,043
42 transactions · 41 stateful · 2026-09-19 17:20:03 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
3.38
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,235,043 · 42 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
1w02w13w24w35w46w57w68w79w814w924w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3b1d828…72e1
0x34b655…2a6f
22 touches
55 conflicts
0x84002f47…4680
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001f
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…002f
0x1b6862…e19c
18 touches
36 conflicts
0x0a6cb118…4caa
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 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
55 conflicts on slot 0xd3b1d828e6…0872e1
Audit this contract →
← previous block·next block →recent activity