← previous blocknext block →recent activity
Analyzing
Block #103,993,559
22 transactions · 18 stateful · 2026-09-11 20:41:40 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,993,559 · 22 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
1w05w06w07w18w19w212w216w317w418w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ec3987…75d8
0x34b655…2a6f
8 touches
6 conflicts
0x9a6fdbc9…1282
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x818e1296…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x94a3fb3f…7515
0x34b655…2a6f
4 touches
1 conflict
0x9d9f3717…44e7
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x25ec39879a…4b75d8
Audit this contract →
← previous block·next block →recent activity