← previous blocknext block →recent activity
Analyzing
Block #106,435,141
23 transactions · 21 stateful · 2026-09-20 10:07:02 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
2.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,435,141 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w313w414w515w616w717w718w819w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x8d664414…3344
0x34b655…2a6f
14 touches
21 conflicts
0xf2d034de…f617
0x34b655…2a6f
10 touches
10 conflicts
0x6da5efbe…7e01
0x34b655…2a6f
8 touches
6 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity