pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,374,897
← previous block
next block →
recent activity
Analyzing
Block #96,374,897
8 transactions · 7 stateful · 2026-08-16 02:50:24 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,374,897
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
#5
0x3f5c179b
#6
execFwdPositionOpsV2
#7
setData
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb571f1fc…9f6a
0x34b655…2a6f
4 touches
1 conflict
0xe1cec2e5…fc35
0x34b655…2a6f
4 touches
1 conflict
0xf40e9839…0001
0x34b655…2a6f
4 touches
1 conflict
0x24d7d3f6…743b
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x427dec7f…61c6
0x34b655…2a6f
2 touches
0 conflicts
0x453ec9be…0093
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity