← previous blocknext block →recent activity
Analyzing
Block #106,809,482
20 transactions · 19 stateful · 2026-09-21 17:32:07 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,809,482 · 20 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
1w02w13w24w35w07w210w111w212w414w315w416w517w619w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66f87924…e03c
0x34b655…2a6f
14 touches
21 conflicts
0xd77fad8d…c5da
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd4c913d7…343b
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 0x66f87924a5…c2e03c
Audit this contract →
← previous block·next block →recent activity