pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,202,608
← previous block
next block →
recent activity
Analyzing
Block #95,202,608
8 transactions · 6 stateful · 2026-08-12 00:18:55 UTC
Parallelism
50
/100
Blocked
50
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,202,608
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
placeAndExecuteMarketSell
· blocks 3
#5
updateDataFeedsValuesPartial
#6
0x6a7bbc67
#7
setData
#2
placeAndExecuteMarketSell
· blocks 2
#3
placeAndExecuteMarketBuy
· blocks 1
#4
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0xc73b4c16…9037
0x40c49f…2af0
5 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x69f200cf…329b
0x40c49f…2af0
3 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x3040553c…5e28
0x754704…b603
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
3 conflicts on slot
0x6518075e89…5f2b17
Audit this contract →
← previous block
·
next block →
recent activity