pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,474,262
← previous block
next block →
recent activity
Analyzing
Block #98,474,262
16 transactions · 9 stateful · 2026-08-23 12:05:25 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,474,262
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xd524a9da
#2
createModule
#3
executePacked
#4
main_all
#5
main_all
#6
0x59558d29
#7
0xe3a3c9cc
#8
0x62be7533
#9
execFwdPositionOpsV2
#10
updateDataFeedsValuesPartial
#11
0x0c7abd22
#12
execOrders
#13
setData
#14
execOrders
#15
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
0x5562cbaa…c417
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x13e1d7bb…87a9
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