← previous blocknext block →recent activity
Analyzing
Block #106,469,294
32 transactions · 30 stateful · 2026-09-20 12:58:58 UTC
Parallelism
59/100
Blocked
63%
Avg conflicts / tx
2.66
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,469,294 · 32 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w212w213w314w417w518w620w721w822w923w1024w925w1026w1127w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9a6e112…69cc
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
12 touches
15 conflicts
0x02397184…a64f
0x34b655…2a6f
10 touches
10 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
10 touches
10 conflicts
0x2aab0897…78f7
0x34b655…2a6f
8 touches
6 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xc9a6e112ce…9769cc
Audit this contract →
← previous block·next block →recent activity