pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,103,836
← previous block
next block →
recent activity
Analyzing
Block #99,103,836
15 transactions · 15 stateful · 2026-08-25 17:35:41 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
#99,103,836
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x41a8f47c
#2
0xab083028
#3
0x6ad2e98b
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
0x5acec890
#7
0x5acec890
#8
0x5acec890
#9
0x5acec890
#10
0x59558d29
#11
execFwdPositionOpsV2
#12
forward
#13
0xed82b078
#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
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x57f2a444…88a5
0x754704…b603
2 touches
0 conflicts
0x5f55f2c8…8f11
0x754704…b603
2 touches
0 conflicts
0x69c8bf4a…2ed0
0x754704…b603
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