pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,972,599
← previous block
next block →
recent activity
Analyzing
Block #94,972,599
13 transactions · 11 stateful · 2026-08-11 05:01:09 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,972,599
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 1
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
placeAndExecuteMarketSell
#6
execute
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
0x6a7aad0d
#11
setData
#12
0xcf9a83…d29d
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaade665d…4c09
0x065c9d…c394
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x2b5101ac…090b
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x51ca3051…0972
0x3bd359…433a
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity