pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,593,458
← previous block
next block →
recent activity
Analyzing
Block #95,593,458
6 transactions · 6 stateful · 2026-08-13 09:18:24 UTC
Parallelism
50
/100
Blocked
33
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,593,458
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
setData
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
6 touches
3 conflicts
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xbb96f8af…205f
0x34b655…2a6f
4 touches
1 conflict
0x466c9e6a…e9de
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x98a1bad6…5130
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x98d1e7bb…8483
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
3 conflicts on slot
0x0672e4a279…2f8d1f
Audit this contract →
← previous block
·
next block →
recent activity