pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,777,855
← previous block
next block →
recent activity
Analyzing
Block #98,777,855
12 transactions · 9 stateful · 2026-08-24 14:08:48 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,777,855
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#2
updatePrices
#5
updateDataFeedsValuesPartial
#6
handleOps
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
execOrders
#10
setData
#11
execOrders
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x89a4b0a3…2106
0x000000…a032
2 touches
0 conflicts
0xecdbcc69…49e4
0x2fd4ee…dfbf
2 touches
0 conflicts
0x00000000…0036
0x35a73b…6042
2 touches
0 conflicts
0x2598f50e…8323
0x35a73b…6042
2 touches
0 conflicts
0x5c29dbf9…cdba
0x35a73b…6042
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:
0xbb3f3cb7…74e046
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity