← previous blocknext block →recent activity
Analyzing
Block #105,462,122
24 transactions · 23 stateful · 2026-09-17 00:27:25 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,462,122 · 24 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
1w02w13w07w29w110w112w114w217w319w220w321w422w523w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb1e37cb…90c9
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc4d98fb1…c354
0x40c49f…2af0
8 touches
6 conflicts
0xc2696b1d…5a82
0x34b655…2a6f
8 touches
6 conflicts
0xa4311026…ca36
0x40c49f…2af0
7 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xdc9526ab…def7
0x40c49f…2af0
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
10 conflicts on slot 0xdb1e37cb5e…7790c9
Audit this contract →
← previous block·next block →recent activity