pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,478,902
← previous block
next block →
recent activity
Analyzing
Block #94,478,902
9 transactions · 8 stateful · 2026-08-09 11:36:29 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,478,902
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
placeAndExecuteMarketSell
· blocks 1
#7
0x6a7866b5
#8
setData
#2
execPerpOps
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x4e00bf91…ec06
0x065c9d…c394
3 touches
1 conflict
0x0a2300ab…81c7
0x34b655…2a6f
2 touches
0 conflicts
0x0bbe8ee6…4ede
0x34b655…2a6f
2 touches
0 conflicts
0x156552f7…c066
0x34b655…2a6f
2 touches
0 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
2 touches
0 conflicts
0x3270d9f8…099a
0x34b655…2a6f
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x0778475bb2…63bd75
Audit this contract →
← previous block
·
next block →
recent activity