← previous blocknext block →recent activity
Analyzing
Block #105,849,692
32 transactions · 32 stateful · 2026-09-18 08:59:31 UTC
Parallelism
50/100
Blocked
72%
Avg conflicts / tx
3.53
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,849,692 · 32 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w08w19w210w211w313w214w315w416w517w618w719w820w921w1022w1124w1326w1529w131w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dccd2a9…2790
0x34b655…2a6f
18 touches
36 conflicts
0x307514a8…4e79
0x34b655…2a6f
16 touches
28 conflicts
0x2827ae77…4368
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xc10b903d…2f54
0x34b655…2a6f
12 touches
15 conflicts
0x69f0d775…13f5
0x34b655…2a6f
12 touches
15 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 0x9dccd2a98b…6d2790
Audit this contract →
← previous block·next block →recent activity