pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,573,248
← previous block
next block →
recent activity
Analyzing
Block #93,573,248
19 transactions · 15 stateful · 2026-08-06 07:25:47 UTC
Parallelism
95
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,573,248
· 19 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
execOrders
#4
execOrders
#5
execPerpOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
execute
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
setData
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#17
execOrders
#18
0xc7e3ec2c
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
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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