← previous blocknext block →recent activity
Analyzing
Block #106,420,452
18 transactions · 17 stateful · 2026-09-20 08:53:06 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,420,452 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w19w010w111w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe77c166e…c7e9
0x34b655…2a6f
8 touches
6 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
8 touches
6 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7a903e28…f9ef
0x34b655…2a6f
4 touches
1 conflict
0xa120845a…e1e4
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xe77c166ef9…e1c7e9
Audit this contract →
← previous block·next block →recent activity