pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,425,888
← previous block
next block →
recent activity
Analyzing
Block #96,425,888
10 transactions · 9 stateful · 2026-08-16 07:06:50 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,425,888
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
execOrders
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0xc925b3a5
#8
setData
· blocks 1
#4
execFwdPositionOpsV2
· blocks 1
#9
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19439a65…eb51
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xe00608f8…edc2
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
2 touches
0 conflicts
0x312e4698…54c0
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
0x19439a65ca…d4eb51
Audit this contract →
← previous block
·
next block →
recent activity