pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,594,044
← previous block
next block →
recent activity
Analyzing
Block #98,594,044
13 transactions · 11 stateful · 2026-08-23 22:25:42 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,594,044
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execute
#3
0xab083028
#4
0x59558d29
#5
0x5acec890
· blocks 1
#7
execFwdPositionOpsV2
#8
verifyOracleProofV2
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
setData
#12
execOrders
#6
0x928e4afa
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x1aa8e8ba…8954
0x34b655…2a6f
2 touches
0 conflicts
0x1c389468…6b0e
0x34b655…2a6f
2 touches
0 conflicts
0x271d9d05…67de
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