pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,879,755
← previous block
next block →
recent activity
Analyzing
Block #93,879,755
14 transactions · 10 stateful · 2026-08-07 09:06:40 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,879,755
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
execPerpOps
#4
execPerpOps
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0x3f5c179b
#8
0x29eed2d3
#9
execFwdPositionOps
· blocks 1
#10
0x6a75a098
#11
setData
#13
execOrders
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x16eb5040…a048
0x34b655…2a6f
2 touches
0 conflicts
0x8743e1ba…8331
0x34b655…2a6f
2 touches
0 conflicts
0x8966e74c…f328
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eeb
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
0x08330b3687…a7ae29
Audit this contract →
← previous block
·
next block →
recent activity