← previous blocknext block →recent activity
Analyzing
Block #106,189,153
24 transactions · 22 stateful · 2026-09-19 13:29:00 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,189,153 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w111w213w315w418w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e1d11e9…61de
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0x26bb6db7…f862
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
10 conflicts on slot 0x3e1d11e9a7…8861de
Audit this contract →
← previous block·next block →recent activity