pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,259,683
← previous block
next block →
recent activity
Analyzing
Block #96,259,683
9 transactions · 7 stateful · 2026-08-15 17:10:55 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,259,683
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xa96df62f
#5
execFwdPositionOpsV2
· blocks 1
#7
execOrders
#8
setData
#2
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00d7ad92…290f
0x34b655…2a6f
2 touches
0 conflicts
0x1c3c9acb…e2b0
0x34b655…2a6f
2 touches
0 conflicts
0x1c97ceaf…d70a
0x34b655…2a6f
2 touches
0 conflicts
0x29c1a140…099f
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
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
0x91cdfdebc5…487feb
Audit this contract →
← previous block
·
next block →
recent activity