pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,869,660
← previous block
next block →
recent activity
Analyzing
Block #94,869,660
11 transactions · 10 stateful · 2026-08-10 20:23:26 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,869,660
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
repayWithCollateral
#4
executeBatch
#5
0x94defb17
· blocks 1
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a7a33b5
#10
0x59558d29
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d8ee1c…453d
0x968279…9342
4 touches
1 conflict
0xf5d8ee1c…4540
0x968279…9342
4 touches
1 conflict
0xf5d8ee1c…4541
0x968279…9342
4 touches
1 conflict
0xf5d8ee1c…4543
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x9ce4fe1c…c1ca
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
0xf5d8ee1c39…ce453d
Audit this contract →
← previous block
·
next block →
recent activity