← previous blocknext block →recent activity
Analyzing
Block #105,851,397
28 transactions · 27 stateful · 2026-09-18 09:08:06 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
0.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,851,397 · 28 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
1w02w13w24w35w37w48w59w612w013w114w218w419w721w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3a467d1…c539
0x34b655…2a6f
10 touches
10 conflicts
0x5d561a6f…7060
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x580c6fe7…0fe9
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
10 conflicts on slot 0xe3a467d18d…a8c539
Audit this contract →
← previous block·next block →recent activity