pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,552,305
← previous block
next block →
recent activity
Analyzing
Block #98,552,305
13 transactions · 9 stateful · 2026-08-23 18:47:57 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,552,305
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
execPerpOps
#5
execPerpOps
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
updatePosition
#9
0x3f5c179b
#11
execOrders
#12
execOrders
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x75c6d2b3…7771
0x34b655…2a6f
4 touches
1 conflict
0xfde01750…f190
0x34b655…2a6f
4 touches
1 conflict
0x5a65207b…4f30
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x45f562b2…9294
0x2b46c0…1669
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
0x5b37bb6bbf…0aab00
Audit this contract →
← previous block
·
next block →
recent activity