← previous blocknext block →recent activity
Analyzing
Block #106,466,397
21 transactions · 21 stateful · 2026-09-20 12:44:23 UTC
Parallelism
57/100
Blocked
57%
Avg conflicts / tx
2.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,466,397 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w211w212w314w415w516w517w618w719w820w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac5f3ead…0195
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xac5f3eadc9…b00195
Audit this contract →
← previous block·next block →recent activity