pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,390,697
← previous block
next block →
recent activity
Analyzing
Block #98,390,697
13 transactions · 12 stateful · 2026-08-23 05:04:38 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,390,697
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0x8263f5d9
#4
execOrders
· blocks 1
#5
execOrder
· blocks 1
#6
0x59558d29
#7
forward
#8
execOrder
#10
redeemDelegations
#11
execFwdPositionOpsV2
#12
setData
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeddebb1d…4dd4
0x34b655…2a6f
4 touches
1 conflict
0x89472a26…7ec8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x20492d53…80f9
0x34b655…2a6f
2 touches
0 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
2 touches
0 conflicts
0x417d849e…2005
0x34b655…2a6f
2 touches
0 conflicts
0x4c20d376…0819
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
0xeddebb1d0b…f54dd4
Audit this contract →
← previous block
·
next block →
recent activity