pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,406,816
← previous block
next block →
recent activity
Analyzing
Block #91,406,816
14 transactions · 13 stateful · 2026-07-29 17:45:44 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
#91,406,816
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x0c7abd22
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
0x5a5d9a99
#6
execute
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
forward
#10
execFwdPositionOps
#11
updateDataFeedsValuesPartial
#12
setData
#13
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x58288509…f330
0x065c9d…c394
2 touches
0 conflicts
0x5f86dbd5…77c3
0x065c9d…c394
2 touches
0 conflicts
0xb18712de…29d7
0x065c9d…c394
2 touches
0 conflicts
0xd3a414a4…1323
0x065c9d…c394
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