pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,551,132
← previous block
next block →
recent activity
Analyzing
Block #93,551,132
10 transactions · 9 stateful · 2026-08-06 05:34:37 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,551,132
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
updatePrices
#4
placeAndExecuteMarketSell
#5
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x6a741d65
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2de8d283…473f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x758f26d7…858f
0x01bff4…1071
2 touches
0 conflicts
0xa8e98b9f…5935
0x01bff4…1071
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xf7640726…19a2
0x2a68ba…90c5
2 touches
0 conflicts
0x0a6a5b44…d0e5
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
0x2de8d283ec…54473f
Audit this contract →
← previous block
·
next block →
recent activity