← previous blocknext block →recent activity
Analyzing
Block #106,959,037
40 transactions · 40 stateful · 2026-09-22 06:04:54 UTC
Parallelism
70/100
Blocked
68%
Avg conflicts / tx
1.9
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,959,037 · 40 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w08w09w110w211w212w013w115w016w117w218w319w420w521w622w723w125w128w329w130w231w532w635w938w1039w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0xb66f2f15…e712
0x34b655…2a6f
10 touches
10 conflicts
0x1d81790c…b9f7
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x0a3faaed…8179
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity