pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,555,479
← previous block
next block →
recent activity
Analyzing
Block #93,555,479
11 transactions · 9 stateful · 2026-08-06 05:56:28 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,555,479
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updatePrices
#3
0xeb282f7f
#4
execFwdPositionOps
#6
placeAndExecuteMarketSell
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x821363…7f6d
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5ab7afd1…18a8
0x1efe02…37d6
2 touches
0 conflicts
0x00210867…83b6
0x34b655…2a6f
2 touches
0 conflicts
0x025fef2f…9738
0x34b655…2a6f
2 touches
0 conflicts
0x13a662f6…33e0
0x34b655…2a6f
2 touches
0 conflicts
0x2f358e74…1022
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
0x52b477bcb8…5d7ccf
Audit this contract →
← previous block
·
next block →
recent activity