← previous blocknext block →recent activity
Analyzing
Block #106,207,301
18 transactions · 16 stateful · 2026-09-19 15:00:22 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,207,301 · 18 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
1w02w13w04w16w07w18w212w113w214w315w417w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15e313f3…9aa1
0x34b655…2a6f
10 touches
10 conflicts
0x5d22710e…af04
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x4e58f1d6…2fca
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
10 conflicts on slot 0x15e313f3b8…fa9aa1
Audit this contract →
← previous block·next block →recent activity