← previous blocknext block →recent activity
Analyzing
Block #103,040,892
20 transactions · 19 stateful · 2026-09-08 12:35:55 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,040,892 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w210w111w214w215w316w417w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac389ba9…8b45
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xf279b789…d3c3
0x34b655…2a6f
8 touches
6 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity