← previous blocknext block →recent activity
Analyzing
Block #105,851,997
28 transactions · 27 stateful · 2026-09-18 09:11:07 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.68
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,851,997 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w28w09w213w317w418w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
18 touches
36 conflicts
0x9e5939a7…9ecc
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x4abfb389…18f4
0x34b655…2a6f
10 touches
10 conflicts
0xee8237bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0x421e897b…37da
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
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
36 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity