pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,675,416
← previous block
next block →
recent activity
Analyzing
Block #98,675,416
10 transactions · 10 stateful · 2026-08-24 05:29:26 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,675,416
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x8263f5d9
#2
0x928e4afa
#3
0x59558d29
#4
setData
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#8
0xed82b078
#9
0x6a8bd72d
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00f19757…9252
0x34b655…2a6f
2 touches
0 conflicts
0x02dc2e29…01a3
0x34b655…2a6f
2 touches
0 conflicts
0x2410db78…bf7a
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x7ec9cda3…6ddb
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
0x41c5638713…86a8f6
Audit this contract →
← previous block
·
next block →
recent activity