← previous blocknext block →recent activity
Analyzing
Block #106,404,435
34 transactions · 33 stateful · 2026-09-20 07:32:29 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
2.88
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,404,435 · 34 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
1w03w04w17w08w19w010w011w114w215w216w318w420w421w322w523w624w725w726w828w1031w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
20 touches
45 conflicts
0xc656717e…f1e6
0x34b655…2a6f
14 touches
21 conflicts
0xc8e54058…6a98
0x34b655…2a6f
10 touches
10 conflicts
0xd1ed6c82…869d
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
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