pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,188,806
← previous block
next block →
recent activity
Analyzing
Block #93,188,806
11 transactions · 11 stateful · 2026-08-04 23:13:01 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,188,806
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
placeAndExecuteMarketSell
#4
0x94defb17
· blocks 2
#7
0x57368ddf
#8
execFwdPositionOps
#9
setData
#5
0x94defb17
· blocks 1
#10
execOrders
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w2
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x139fb87e…5597
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x037024dd…c93f
0x968279…9342
6 touches
3 conflicts
0x037024dd…c940
0x968279…9342
6 touches
3 conflicts
0x037024dd…c942
0x968279…9342
6 touches
3 conflicts
0x139fb87e…5591
0x968279…9342
6 touches
3 conflicts
0x139fb87e…5592
0x968279…9342
6 touches
3 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:
0x96827978…f09342
3 conflicts on slot
0x139fb87e9e…d35597
Audit this contract →
← previous block
·
next block →
recent activity