pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,546,060
← previous block
next block →
recent activity
Analyzing
Block #96,546,060
10 transactions · 9 stateful · 2026-08-16 17:11:34 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,546,060
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrder
#3
execOrder
· blocks 1
#5
execFwdPositionOpsV2
· blocks 1
#7
0x3f5c179b
#8
execOrders
#9
setData
#4
execOrder
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0x008e7cea…d341
0x34b655…2a6f
4 touches
1 conflict
0x0abf7b77…0d80
0x34b655…2a6f
2 touches
0 conflicts
0x1c255c26…11dd
0x34b655…2a6f
2 touches
0 conflicts
0x27771b95…6161
0x34b655…2a6f
2 touches
0 conflicts
0x4ae3b148…7ed2
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
1 conflict on slot
0x08636046fc…69e60f
Audit this contract →
← previous block
·
next block →
recent activity