← previous blocknext block →recent activity
Analyzing
Block #95,024,418
29 transactions · 27 stateful · 2026-08-11 09:21:49 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,024,418 · 29 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
1w02w04w05w06w17w28w39w111w213w315w116w217w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x342222e8…2ec4
0x34b655…2a6f
4 touches
1 conflict
0x50dfdd6a…fc6a
0x34b655…2a6f
4 touches
1 conflict
0x700c7319…e584
0x34b655…2a6f
4 touches
1 conflict
0x71efc59e…1434
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
15 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity