← previous blocknext block →recent activity
Analyzing
Block #106,469,298
24 transactions · 24 stateful · 2026-09-20 12:58:59 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
2.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,469,298 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w59w410w011w112w116w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02397184…a64f
0x34b655…2a6f
14 touches
21 conflicts
0xfa81f368…5ed8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
12 touches
15 conflicts
0x524f0872…0d12
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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 0x023971841b…3fa64f
Audit this contract →
← previous block·next block →recent activity