pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,120,823
← previous block
next block →
recent activity
Analyzing
Block #99,120,823
10 transactions · 7 stateful · 2026-08-25 19:01:15 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,120,823
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#4
revealHourly
#5
execFwdPositionOpsV2
#6
setData
#7
0x36326531
#8
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2d8af24…4750
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0005
0x2a10b1…5769
2 touches
0 conflicts
0x3ec842e8…dfa2
0x34b655…2a6f
2 touches
0 conflicts
0x7d0a36f0…174e
0x34b655…2a6f
2 touches
0 conflicts
0x8f7dc0bc…552c
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eeb
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xb2d8af2470…774750
Audit this contract →
← previous block
·
next block →
recent activity