← previous blocknext block →recent activity
Analyzing
Block #106,934,095
21 transactions · 20 stateful · 2026-09-22 03:59:20 UTC
Parallelism
62/100
Blocked
65%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,934,095 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w19w010w111w212w313w414w515w616w718w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46483cb1…e7ca
0x34b655…2a6f
16 touches
28 conflicts
0xf0e6cbe4…22de
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x75e73565…45f9
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0x46483cb14f…c1e7ca
Audit this contract →
← previous block·next block →recent activity