pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,675,917
← previous block
next block →
recent activity
Analyzing
Block #93,675,917
13 transactions · 11 stateful · 2026-08-06 16:01:55 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,675,917
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrder
· blocks 1
#3
execPerpOps
#4
execPerpOps
#5
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
placeAndExecuteMarketSell
#9
0x3f5c179b
#10
0xed82b078
#11
0x6a74b06b
#12
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0x34501e59…925f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x27754bd4…96ae
0x34b655…2a6f
2 touches
0 conflicts
0x464085b1…499b
0x34b655…2a6f
2 touches
0 conflicts
0x5e2fca4c…cf4d
0x34b655…2a6f
2 touches
0 conflicts
0x615e7c53…e353
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
0xc6000ba5c1…988d65
Audit this contract →
← previous block
·
next block →
recent activity