pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,006,010
← previous block
next block →
recent activity
Analyzing
Block #95,006,010
15 transactions · 11 stateful · 2026-08-11 07:49:11 UTC
Parallelism
87
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,006,010
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xab083028
· blocks 1
#4
0x6a7ad46f
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
placeAndExecuteMarketSell
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
updateDataFeedsValuesPartial
#12
setData
#13
0xb21329…befb
#14
0x59558d29
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x02ddab41…cc5f
0x065c9d…c394
2 touches
0 conflicts
0x2c59f2e3…a11f
0x065c9d…c394
2 touches
0 conflicts
0xab737daa…b67c
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
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