pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,978,300
← previous block
next block →
recent activity
Analyzing
Block #94,978,300
14 transactions · 12 stateful · 2026-08-11 05:29:49 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,978,300
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
execFwdPositionOps
#7
setData
#8
placeAndExecuteMarketSell
#9
0x94defb17
· blocks 1
#11
execFwdPositionOps
#12
transferWithAuthorization
#13
0x6a7ab3c5
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x514232bb…e30e
0x968279…9342
4 touches
1 conflict
0x514232bb…e30f
0x968279…9342
4 touches
1 conflict
0x514232bb…e311
0x968279…9342
4 touches
1 conflict
0xc76895a5…8d8a
0x968279…9342
4 touches
1 conflict
0xc76895a5…8d8b
0x968279…9342
4 touches
1 conflict
0xc76895a5…8d8e
0x968279…9342
4 touches
1 conflict
0xc76895a5…8d8f
0x968279…9342
4 touches
1 conflict
0xc76895a5…8d90
0x968279…9342
4 touches
1 conflict
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:
0x96827978…f09342
1 conflict on slot
0x514232bb44…97e30e
Audit this contract →
← previous block
·
next block →
recent activity