pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,787,116
← previous block
next block →
recent activity
Analyzing
Block #96,787,116
15 transactions · 9 stateful · 2026-08-17 13:23:59 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
#96,787,116
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x4f819052
#2
0x008a1463
#3
0x50a0b275
#4
main_all
#5
main_all
#6
0xb414539a
#7
0x5acec890
#8
execOrders
#9
execFwdPositionOpsV2
#10
0x62be7533
#11
execFwdPositionOpsV2
#12
updateDataFeedsValuesPartial
#13
updateDataFeedsValuesPartial
#14
setData
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
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0x4356c9e6…9bf4
0x3bd359…433a
2 touches
0 conflicts
0x63f5c02f…6853
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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