← previous blocknext block →recent activity
Analyzing
Block #105,870,017
22 transactions · 20 stateful · 2026-09-18 10:41:48 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,870,017 · 22 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
1w02w13w24w36w07w08w09w110w111w212w313w414w515w616w721w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62eba3f0…75ab
0x34b655…2a6f
16 touches
28 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0x0efc210e…70ab
0x34b655…2a6f
10 touches
10 conflicts
0x4d42f16e…a6c6
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
28 conflicts on slot 0x62eba3f0b1…8675ab
Audit this contract →
← previous block·next block →recent activity