← previous blocknext block →recent activity
Analyzing
Block #105,921,669
32 transactions · 30 stateful · 2026-09-18 15:02:39 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1.41
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,921,669 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w314w015w116w217w318w427w328w529w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6615a36…3cf0
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x17a7f697…dcb2
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
15 conflicts on slot 0xc6615a36ef…7f3cf0
Audit this contract →
← previous block·next block →recent activity