← previous blocknext block →recent activity
Analyzing
Block #95,721,089
8 transactions · 6 stateful · 2026-08-13 20:01:25 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,721,089 · 8 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
1w02w13w24w37w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x17326681…7b86
0x34b655…2a6f
4 touches
1 conflict
0xf62c017d…e543
0x34b655…2a6f
4 touches
1 conflict
0xcf907a0c…f7da
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
2 touches
0 conflicts
0x6a10a152…a08f
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a2
0x34b655…2a6f
2 touches
0 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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity