← previous blocknext block →recent activity
Analyzing
Block #106,540,890
28 transactions · 27 stateful · 2026-09-20 18:59:18 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
2.36
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,540,890 · 28 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
1w02w13w24w39w010w111w214w315w317w418w519w620w721w822w924w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe05a4bed…69cb
0x34b655…2a6f
18 touches
36 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
18 touches
36 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
36 conflicts on slot 0xe05a4bedea…e369cb
Audit this contract →
← previous block·next block →recent activity