pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,498,915
← previous block
next block →
recent activity
Analyzing
Block #98,498,915
17 transactions · 12 stateful · 2026-08-23 14:09:31 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,498,915
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x756d94…70b1
#2
0xb75483…0c4a
#3
0xa96df62f
#4
0xab083028
#5
0x6ad2e98b
#6
execOrders
#7
0x59558d29
#8
execPerpOps
#9
execPerpOps
#10
execPerpOps
#11
execPerpOps
#12
execOrder
#13
execFwdPositionOpsV2
#14
execFwdPositionOpsV2
#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
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x543da691…8f99
0x34b655…2a6f
2 touches
0 conflicts
0x63f4382e…57b6
0x34b655…2a6f
2 touches
0 conflicts
0x652acceb…1651
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.
← previous block
·
next block →
recent activity