← previous blocknext block →recent activity
Analyzing
Block #109,176,957
25 transactions · 23 stateful · 2026-09-30 00:18:01 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,176,957 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w011w115w116w217w318w419w121w022w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b076c1b…ca73
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xbefdde57…cd0e
0x34b655…2a6f
4 touches
1 conflict
0xc4c059d8…185d
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x4b076c1b01…72ca73
Audit this contract →
← previous block·next block →recent activity