pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,665,964
← previous block
next block →
recent activity
Analyzing
Block #93,665,964
13 transactions · 9 stateful · 2026-08-06 15:11:53 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,665,964
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
placeAndExecuteMarketSell
#5
0x3f5c179b
#7
forward
#8
batchUpdate
#9
updateDataFeedsValuesPartial
#10
0x6a74a4b1
#11
setData
#12
execOrders
#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
0xbb384cb4…9cde
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
0x2dd03fb9…6243
0x34b655…2a6f
2 touches
0 conflicts
0x2e7a0c1d…caaf
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x6507044e…bcd6
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
0xbb384cb450…1b9cde
Audit this contract →
← previous block
·
next block →
recent activity