← previous blocknext block →recent activity
Analyzing
Block #105,869,540
30 transactions · 28 stateful · 2026-09-18 10:39:24 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,869,540 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w010w012w013w119w128w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0x16bba458…258c
0x34b655…2a6f
8 touches
6 conflicts
0x2fae69f2…54d5
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x3018a378…d7bb
0x34b655…2a6f
6 touches
3 conflicts
0x3b59f067…333f
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
15 conflicts on slot 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity