← previous blocknext block →recent activity
Analyzing
Block #103,987,668
13 transactions · 12 stateful · 2026-09-11 20:11:44 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,987,668 · 13 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
1w05w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb01e7e01…4f1f
0x34b655…2a6f
4 touches
1 conflict
0xcd1306ad…f1b8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x28fe17d2…4cc0
0x34b655…2a6f
2 touches
0 conflicts
0x2ed6b2ea…c86d
0x34b655…2a6f
2 touches
0 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x45a7c210…d2d7
0x34b655…2a6f
2 touches
0 conflicts
0x574628e9…dcc3
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 0xb01e7e0125…e44f1f
Audit this contract →
← previous block·next block →recent activity