← previous blocknext block →recent activity
Analyzing
Block #106,467,812
29 transactions · 24 stateful · 2026-09-20 12:51:31 UTC
Parallelism
66/100
Blocked
58%
Avg conflicts / tx
1.41
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,467,812 · 29 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
1w02w13w24w310w411w013w414w515w516w617w718w819w924w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
12 touches
15 conflicts
0x611a16a4…f6b1
0x34b655…2a6f
12 touches
15 conflicts
0x3cc04064…aa09
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be13
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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