pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,297,797
← previous block
next block →
recent activity
Analyzing
Block #94,297,797
9 transactions · 9 stateful · 2026-08-08 20:16:39 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,297,797
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executeBatch
#2
placeAndExecuteMarketSell
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#3
placeAndExecuteMarketBuy
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b4e1f8…808f
0x34b655…2a6f
4 touches
1 conflict
0xc1f6acda…6abb
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x1f90c45d…89c2
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x693b762e…1fcd
0xe52b14…7230
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
0xb9b4e1f8a2…0d808f
Audit this contract →
← previous block
·
next block →
recent activity