← previous blocknext block →recent activity
Analyzing
Block #105,760,517
20 transactions · 20 stateful · 2026-09-18 01:29:16 UTC
Parallelism
45/100
Blocked
55%
Avg conflicts / tx
1.95
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,760,517 · 20 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w48w513w514w615w716w817w918w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1204f20c…3f98
0x34b655…2a6f
14 touches
21 conflicts
0x0efc210e…70ab
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x6aa624fd…a851
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0x1204f20c06…333f98
Audit this contract →
← previous block·next block →recent activity