← previous blocknext block →recent activity
Analyzing
Block #105,930,551
22 transactions · 20 stateful · 2026-09-18 15:47:22 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,930,551 · 22 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
1w02w13w04w26w37w08w111w412w113w514w315w416w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17d87f0d…bfc5
0x34b655…2a6f
14 touches
21 conflicts
0xa696c3a6…72bc
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
6 touches
3 conflicts
0x2fba77e7…bea1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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
21 conflicts on slot 0x17d87f0d74…03bfc5
Audit this contract →
← previous block·next block →recent activity