pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,494,898
← previous block
next block →
recent activity
Analyzing
Block #83,494,898
13 transactions · 13 stateful · 2026-06-25 00:44:49 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,494,898
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
batchUpdate
#2
batchUpdate
#3
0x6ad2e98b
#4
batchCancelOrders
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
executeBatch
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
0x6a3c7a79
#11
setData
#12
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
0x36da2372…864b
0x065c9d…c394
2 touches
0 conflicts
0x790efc72…1879
0x065c9d…c394
2 touches
0 conflicts
0x7b9aa0b3…aa6c
0x065c9d…c394
2 touches
0 conflicts
0x93a9f6e3…e711
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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