← previous blocknext block →recent activity
Analyzing
Block #106,185,242
30 transactions · 28 stateful · 2026-09-19 13:09:19 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
2.1
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,185,242 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w19w210w311w119w521w422w523w624w725w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892587dc…c0ff
0x34b655…2a6f
18 touches
36 conflicts
0xc44003b5…2dac
0x34b655…2a6f
14 touches
21 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
12 touches
15 conflicts
0xd6071d1d…496c
0x1b6862…e19c
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
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
36 conflicts on slot 0x892587dc9c…f8c0ff
Audit this contract →
← previous block·next block →recent activity