← previous blocknext block →recent activity
Analyzing
Block #106,420,187
29 transactions · 29 stateful · 2026-09-20 08:51:46 UTC
Parallelism
45/100
Blocked
66%
Avg conflicts / tx
3.34
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,420,187 · 29 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
1w02w13w24w28w39w311w412w514w316w818w1019w1121w1323w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97ab5020…3f1b
0x34b655…2a6f
18 touches
36 conflicts
0xebf19faa…72cb
0x34b655…2a6f
18 touches
36 conflicts
0x061f6bff…f3b0
0x34b655…2a6f
14 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x5e3014f0…b4e1
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
36 conflicts on slot 0x97ab502036…963f1b
Audit this contract →
← previous block·next block →recent activity