pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,581,734
← previous block
next block →
recent activity
Analyzing
Block #98,581,734
13 transactions · 10 stateful · 2026-08-23 21:21:29 UTC
Parallelism
77
/100
Blocked
20
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,581,734
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
setData
#2
0xab083028
#3
0x5acec890
· blocks 2
#4
execOrders
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#10
execFwdPositionOpsV2
#11
0xa5abed…2d0f
#12
0x603877…8be7
#8
0x928e4afa
· blocks 1
#9
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x192a1fc3…9766
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x427f51fd…bd80
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity