pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,578,991
← previous block
next block →
recent activity
Analyzing
Block #95,578,991
10 transactions · 8 stateful · 2026-08-13 08:05:38 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,578,991
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#9
0x59558d29
#2
execOrder
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
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x021df0f6…5d6f
0x34b655…2a6f
2 touches
0 conflicts
0x0227484c…b688
0x34b655…2a6f
2 touches
0 conflicts
0x5e78c401…7a7e
0x34b655…2a6f
2 touches
0 conflicts
0x6bf3c40e…4f8a
0x34b655…2a6f
2 touches
0 conflicts
0x71f4c564…5b6b
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
0x43fd366775…d0094b
Audit this contract →
← previous block
·
next block →
recent activity