← previous blocknext block →recent activity
Analyzing
Block #106,577,674
30 transactions · 29 stateful · 2026-09-20 22:04:25 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.9
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,577,674 · 30 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
1w02w13w24w35w46w57w011w313w414w520w626w727w828w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20b1228b…2487
0x34b655…2a6f
14 touches
21 conflicts
0x0f0f10dd…05bd
0x34b655…2a6f
12 touches
15 conflicts
0x13b6c9e2…c783
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xfac61869…a561
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
21 conflicts on slot 0x20b1228bdf…a72487
Audit this contract →
← previous block·next block →recent activity