pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,524,500
← previous block
next block →
recent activity
Analyzing
Block #98,524,500
17 transactions · 12 stateful · 2026-08-23 16:23:08 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,524,500
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execute
#2
executePacked
#3
0xa96df62f
#4
0xa9b28aa6
#5
0xab083028
#6
0x59558d29
#7
0xbb1740dd
#8
0xe3a3c9cc
#9
0x62be7533
#10
execFwdPositionOpsV2
#11
0x57368ddf
#12
handleOps
#13
execFwdPositionOpsV2
#14
0x6a8b1ee3
#15
setData
#16
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x9fc2d6f8…6471
0x3bd359…433a
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.
← previous block
·
next block →
recent activity