← previous blocknext block →recent activity
Analyzing
Block #106,570,215
14 transactions · 13 stateful · 2026-09-20 21:26:53 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,570,215 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17d42502…4e7b
0x34b655…2a6f
8 touches
6 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x8bd2d544…9de5
0x34b655…2a6f
4 touches
1 conflict
0x6fd9ae7c…e983
0x1b6862…e19c
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 0x17d42502ba…4f4e7b
Audit this contract →
← previous block·next block →recent activity