← previous blocknext block →recent activity
Analyzing
Block #106,932,434
26 transactions · 24 stateful · 2026-09-22 03:50:59 UTC
Parallelism
62/100
Blocked
71%
Avg conflicts / tx
1.92
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,932,434 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w09w110w211w312w415w618w121w722w423w824w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
14 touches
21 conflicts
0xab981df1…2941
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xec1dd684…b6b3
0x34b655…2a6f
10 touches
10 conflicts
0x66774a98…88c8
0x34b655…2a6f
10 touches
10 conflicts
0x36d207d1…97e0
0x34b655…2a6f
8 touches
6 conflicts
0xd40be9a6…9594
0xd32edf…ff58
7 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 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity