← previous blocknext block →recent activity
Analyzing
Block #103,211,511
20 transactions · 19 stateful · 2026-09-09 02:56:07 UTC
Parallelism
75/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,211,511 · 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
3w04w15w26w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0xfaf08ba6…f2d9
0x34b655…2a6f
4 touches
1 conflict
0x04bd3e5c…bd31
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x0f763490…ff64
0x34b655…2a6f
2 touches
0 conflicts
0x1513b999…b52e
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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity