pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,282,094
← previous block
next block →
recent activity
Analyzing
Block #96,282,094
10 transactions · 9 stateful · 2026-08-15 19:03:39 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,282,094
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0x5acec890
#3
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#6
setData
#7
execFwdPositionOpsV2
#8
transfer
#4
execFwdPositionOpsV2
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427dec7f…61c6
0x34b655…2a6f
6 touches
3 conflicts
0xf40e9839…0001
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x67209a5a…ab0e
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
0x76c4467d…ce28
0x34b655…2a6f
2 touches
0 conflicts
0x941a3210…86ca
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
3 conflicts on slot
0x427dec7fbc…3e61c6
Audit this contract →
← previous block
·
next block →
recent activity