← previous blocknext block →recent activity
Analyzing
Block #105,672,610
18 transactions · 16 stateful · 2026-09-17 18:06:52 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,672,610 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w111w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe77b8759…eea0
0x34b655…2a6f
4 touches
1 conflict
0xf7d0043d…e7b2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x03c639f9…fb2d
0x34b655…2a6f
2 touches
0 conflicts
0x12e605da…9ca3
0x34b655…2a6f
2 touches
0 conflicts
0x1ede1c30…8bed
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity