pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,267,264
← previous block
next block →
recent activity
Analyzing
Block #93,267,264
13 transactions · 13 stateful · 2026-08-05 05:47:28 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,267,264
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
0x94defb17
· blocks 1
#7
forward
#8
forward
#9
execFwdPositionOps
#10
updateDataFeedsValuesPartial
#11
0x6a72cee8
#12
setData
#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
0xf48a8c63…0b00
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
0xce72ece5…88d1
0x968279…9342
4 touches
1 conflict
0xce72ece5…88d2
0x968279…9342
4 touches
1 conflict
0xce72ece5…88d4
0x968279…9342
4 touches
1 conflict
0xf48a8c63…0afb
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
0xf48a8c630c…d20b00
Audit this contract →
← previous block
·
next block →
recent activity