← previous blocknext block →recent activity
Analyzing
Block #106,476,485
21 transactions · 21 stateful · 2026-09-20 13:35:09 UTC
Parallelism
57/100
Blocked
67%
Avg conflicts / tx
1.9
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,476,485 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w18w19w210w311w312w313w414w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f999f4f…be21
0x34b655…2a6f
14 touches
21 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
10 touches
10 conflicts
0xa0685f64…f220
0x34b655…2a6f
8 touches
6 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
8 touches
6 conflicts
0x6ae1e935…797b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x10c19272…7443
0x1b6862…e19c
6 touches
3 conflicts
0xc1da8f73…484c
0x34b655…2a6f
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
21 conflicts on slot 0x1f999f4fc3…0cbe21
Audit this contract →
← previous block·next block →recent activity