← previous blocknext block →recent activity
Analyzing
Block #106,404,311
25 transactions · 25 stateful · 2026-09-20 07:31:52 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
2.12
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,404,311 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w38w09w113w115w416w317w218w419w520w621w722w824w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cc04064…aa09
0x34b655…2a6f
14 touches
21 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
12 touches
15 conflicts
0x2c2761c0…476e
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x0a85a226…83bc
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 0x3cc04064e8…f4aa09
Audit this contract →
← previous block·next block →recent activity