pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,733,972
← previous block
next block →
recent activity
Analyzing
Block #97,733,972
7 transactions · 6 stateful · 2026-08-20 21:45:06 UTC
Parallelism
71
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,733,972
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
· blocks 2
#3
handleOps
#5
0x61d59c2d
#4
execFwdPositionOpsV2
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bc43347…93d4
0x34b655…2a6f
4 touches
1 conflict
0xe41626f9…dd93
0x34b655…2a6f
4 touches
1 conflict
0x01a08f7d…dec6
0x34b655…2a6f
2 touches
0 conflicts
0x0a66d170…5f58
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x246b03e5…3d16
0x34b655…2a6f
2 touches
0 conflicts
0x2bb31955…5e5a
0x34b655…2a6f
2 touches
0 conflicts
0x2e4aa829…4925
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
0x0bc433477d…9e93d4
Audit this contract →
← previous block
·
next block →
recent activity