pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,388,060
← previous block
next block →
recent activity
Analyzing
Block #96,388,060
8 transactions · 7 stateful · 2026-08-16 03:56:36 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,388,060
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
· blocks 1
#3
execFwdPositionOpsV2
#4
updateDataFeedsValuesPartial
#6
setData
#7
0x61d59c2d
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5adda4a7…b840
0x34b655…2a6f
4 touches
1 conflict
0x91c78311…3b17
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x0b9b07b8…b998
0x34b655…2a6f
2 touches
0 conflicts
0x4c86d0e4…e2f1
0x34b655…2a6f
2 touches
0 conflicts
0x4c86d0e4…e2f2
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
0x5adda4a7f8…0cb840
Audit this contract →
← previous block
·
next block →
recent activity