← previous blocknext block →recent activity
Analyzing
Block #105,851,529
42 transactions · 37 stateful · 2026-09-18 09:08:46 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
3.12
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,851,529 · 42 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w08w110w211w012w213w315w418w319w421w122w523w424w625w726w827w935w140w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
30 touches
105 conflicts
0xac389ba9…8b45
0x34b655…2a6f
24 touches
66 conflicts
0xc10b903d…2f54
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x4681609f…6493
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x8f940d48…35bc
0x34b655…2a6f
10 touches
10 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
105 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity