← previous blocknext block →recent activity
Analyzing
Block #106,959,242
15 transactions · 15 stateful · 2026-09-22 06:05:56 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,959,242 · 15 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
1w02w13w14w26w37w412w213w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x967df1b1…e02e
0x34b655…2a6f
10 touches
10 conflicts
0xa4a1ecf7…9e63
0x34b655…2a6f
10 touches
10 conflicts
0xf971f10a…3c2c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdb95e18e…c73d
0x1b6862…e19c
4 touches
1 conflict
0x49b9fdd5…9c16
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
10 conflicts on slot 0x967df1b170…cbe02e
Audit this contract →
← previous block·next block →recent activity