pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,496,320
← previous block
next block →
recent activity
Analyzing
Block #99,496,320
10 transactions · 8 stateful · 2026-08-27 02:31:13 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,496,320
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x5acec890
· blocks 1
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
setData
#7
execFwdPositionOpsV2
#8
0xb50661…a10e
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf70e146…f042
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x0baf5ede…b815
0x34b655…2a6f
4 touches
1 conflict
0x1032f16c…a9b1
0x34b655…2a6f
2 touches
0 conflicts
0x16d77246…bac5
0x34b655…2a6f
2 touches
0 conflicts
0x280aaa58…1c52
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
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
0xcf70e14620…71f042
Audit this contract →
← previous block
·
next block →
recent activity