← previous blocknext block →recent activity
Analyzing
Block #95,163,651
10 transactions · 9 stateful · 2026-08-11 21:02:59 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,163,651 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01fd2f1a…f8f2
0x34b655…2a6f
8 touches
6 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x82a21578…a099
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xea154cbb…f280
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
6 conflicts on slot 0x01fd2f1a14…58f8f2
Audit this contract →
← previous block·next block →recent activity