pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,277,413
← previous block
next block →
recent activity
Analyzing
Block #95,277,413
10 transactions · 9 stateful · 2026-08-12 06:44:04 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
#95,277,413
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeabbe9d8
#2
0x4d8dc985
· blocks 1
#3
updatePrices
#4
0x0f6795d9
#6
placeAndExecuteMarketSell
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x59558d29
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0x35a2c1ad…f105
0x0a3323…0a3c
2 touches
0 conflicts
0x52c63247…ce02
0x0a3323…0a3c
2 touches
0 conflicts
0x7ebd6e44…b6f3
0x6f4756…dd5b
2 touches
0 conflicts
0x3904724e…9a80
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:
Perpl
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity