pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,611,947
← previous block
next block →
recent activity
Analyzing
Block #97,611,947
10 transactions · 10 stateful · 2026-08-20 11:21:20 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,611,947
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrder
· blocks 1
#4
0x5acec890
· blocks 1
#6
executeBatch
#7
0xed82b078
#8
setData
#9
0x59558d29
#3
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0x3102b5f3…ccba
0x34b655…2a6f
4 touches
1 conflict
0xb7b446d2…2006
0x34b655…2a6f
4 touches
1 conflict
0x03986160…5966
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
2 touches
0 conflicts
0x422d5490…52d9
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
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
0xab981df1f6…082941
Audit this contract →
← previous block
·
next block →
recent activity