pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,408,226
← previous block
next block →
recent activity
Analyzing
Block #91,408,226
11 transactions · 11 stateful · 2026-07-29 17:52:55 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,408,226
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
execFwdPositionOps
#7
forward
#8
approve
#9
approve
#10
setData
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x45550d84…bc01
0x065c9d…c394
2 touches
0 conflicts
0x4be1ef6c…f5ad
0x065c9d…c394
2 touches
0 conflicts
0x505da030…16a3
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
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.
The bottleneck
Throughput-killer:
0x48cba278…e2b48b
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity