← previous blocknext block →recent activity
Analyzing
Block #103,050,216
35 transactions · 31 stateful · 2026-09-08 13:22:50 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
1.54
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #103,050,216 · 35 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
1w02w13w24w35w06w17w211w213w120w422w524w627w329w332w734w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xb358a740…cf65
0x34b655…2a6f
10 touches
10 conflicts
0x25180879…8191
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd5c98027…9fd9
0x34b655…2a6f
8 touches
6 conflicts
0x23559b91…e918
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity