← previous blocknext block →recent activity
Analyzing
Block #106,207,867
25 transactions · 23 stateful · 2026-09-19 15:03:13 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,207,867 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w011w013w016w217w118w319w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9470055…bbf8
0x34b655…2a6f
10 touches
10 conflicts
0xd597209e…9800
0x34b655…2a6f
8 touches
6 conflicts
0x873436b8…98e7
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0x94eef853…f8ec
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd996735f…8735
0x1b6862…e19c
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 0xf94700553e…5dbbf8
Audit this contract →
← previous block·next block →recent activity