pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,289,603
← previous block
next block →
recent activity
Analyzing
Block #93,289,603
15 transactions · 11 stateful · 2026-08-05 07:39:48 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
#93,289,603
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execute
#2
executePacked
#3
0x1094dc9f
#4
0x50a0b275
#5
0x0c7abd22
#6
0xbb1740dd
#7
0x5acec890
#8
0x5acec890
#9
execFwdPositionOps
#10
updateDataFeedsValuesPartial
#11
0x6a72e93c
#12
setData
#13
execOrders
#14
0x59558d29
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
0x4044deaf…d090
0x065c9d…c394
2 touches
0 conflicts
0x9e9c0e9e…2c41
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x92d610a6…9a40
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