pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,524,538
← previous block
next block →
recent activity
Analyzing
Block #98,524,538
11 transactions · 11 stateful · 2026-08-23 16:23:20 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
#98,524,538
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
#3
0x59558d29
#4
0x5acec890
· blocks 1
#5
0xeb282f7f
#7
execFwdPositionOpsV2
#8
0xed82b078
#9
0x6a8b1eef
#10
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x1e9a3afd…a6e5
0x34b655…2a6f
2 touches
0 conflicts
0x386d08f4…5a01
0x34b655…2a6f
2 touches
0 conflicts
0x3922cbeb…dc6d
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
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
0x801a6e5726…c1d85c
Audit this contract →
← previous block
·
next block →
recent activity