← previous blocknext block →recent activity
Analyzing
Block #106,408,404
38 transactions · 35 stateful · 2026-09-20 07:52:28 UTC
Parallelism
58/100
Blocked
69%
Avg conflicts / tx
2.74
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,408,404 · 38 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
1w02w03w14w26w311w412w513w614w717w518w622w723w824w926w928w1030w1231w1333w1535w137w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
20 touches
45 conflicts
0x228da3f5…c2bf
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x54563e2b…7469
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
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
45 conflicts on slot 0xd563f3a18c…f494b1
Audit this contract →
← previous block·next block →recent activity