pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,811,975
← previous block
next block →
recent activity
Analyzing
Block #91,811,975
24 transactions · 19 stateful · 2026-07-31 03:45:01 UTC
Parallelism
96
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,811,975
· 24 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x0c7abd22
#2
CreateMemory
#3
CreateMemory
#4
CreateMemory
#5
CreateMemory
#6
CreateMemory
#7
CreateMemory
#8
CreateMemory
#9
CreateMemory
#10
CreateMemory
#11
CreateMemory
#12
CreateMemory
#13
CreateMemory
#14
CreateMemory
#15
CreateMemory
#16
0x57368ddf
#17
execFwdPositionOps
#18
updateDataFeedsValuesPartial
#19
execOrders
#20
execOrders
#21
execOrders
#22
setData
#23
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
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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