pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,434,294
← previous block
next block →
recent activity
Analyzing
Block #98,434,294
13 transactions · 12 stateful · 2026-08-23 08:43:59 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,434,294
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6ad2e98b
#3
0x59558d29
#4
supply
#5
0x928e4afa
· blocks 1
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
0x6a8ab346
#11
setData
#12
execOrders
#6
0x5acec890
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
0x18fcc356…12c2
0x34b655…2a6f
2 touches
0 conflicts
0x23bb9a30…9d2f
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0036
0x39f901…6bdf
2 touches
0 conflicts
0xe6d4f28e…5a6e
0x39f901…6bdf
2 touches
0 conflicts
0xd0192b41…b2c7
0x57ea24…2cec
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