pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,476,875
← previous block
next block →
recent activity
Analyzing
Block #99,476,875
15 transactions · 11 stateful · 2026-08-27 00:53:16 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,476,875
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x6ad2e98b
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0x5acec890
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
execPerpOps
#9
setData
#10
execFwdPositionOpsV2
#11
0x6a8f8af4
#12
execOrders
#13
execOrders
#14
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x80caf0f7…f2de
0x2b46c0…1669
2 touches
0 conflicts
0x915c095e…c1e5
0x2b46c0…1669
2 touches
0 conflicts
0x076b9edf…e35c
0x34b655…2a6f
2 touches
0 conflicts
0x359866c7…de7b
0x34b655…2a6f
2 touches
0 conflicts
0x49b0842d…0a93
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.
← previous block
·
next block →
recent activity