← previous blocknext block →recent activity
Analyzing
Block #106,425,620
17 transactions · 17 stateful · 2026-09-20 09:19:06 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,425,620 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w38w19w411w012w113w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cd9fd28…a158
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xd7e4217d…7c6b
0x34b655…2a6f
6 touches
3 conflicts
0xedf0fd5d…0c8b
0x34b655…2a6f
6 touches
3 conflicts
0xf36202ac…939e
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0x9ff94a68…7ae8
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
15 conflicts on slot 0x7cd9fd286f…a7a158
Audit this contract →
← previous block·next block →recent activity