pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,263,635
← previous block
next block →
recent activity
Analyzing
Block #99,263,635
11 transactions · 11 stateful · 2026-08-26 06:59:50 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,263,635
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5acec890
· blocks 1
#4
0x5acec890
#5
0x59558d29
#6
transferWithAuthorization
#7
setData
#8
execFwdPositionOpsV2
#9
transfer
#10
0x6a8e8f5d
#3
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1af6104a…13f8
0x34b655…2a6f
2 touches
0 conflicts
0x26923160…9f8d
0x34b655…2a6f
2 touches
0 conflicts
0x4602448d…e979
0x34b655…2a6f
2 touches
0 conflicts
0x4a99ba46…452f
0x34b655…2a6f
2 touches
0 conflicts
0x78c01531…e174
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity