pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,456,891
← previous block
next block →
recent activity
Analyzing
Block #99,456,891
13 transactions · 12 stateful · 2026-08-26 23:12:40 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,456,891
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x8263f5d9
#4
0x5acec890
#5
0x5acec890
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x59558d29
#8
0x59558d29
#10
0x6a8f7360
#11
setData
· blocks 1
#9
execFwdPositionOpsV2
#12
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe2d50773…c39e
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1338acf5…2413
0x065c9d…c394
2 touches
0 conflicts
0x28e572ad…9acd
0x065c9d…c394
2 touches
0 conflicts
0x4ce8543e…7a3e
0x065c9d…c394
2 touches
0 conflicts
0xed1e6665…2d3f
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity