pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,361,288
← previous block
next block →
recent activity
Analyzing
Block #99,361,288
13 transactions · 11 stateful · 2026-08-26 15:11:13 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,361,288
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a8f0289
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0x5acec890
#5
0x59558d29
#6
execPerpOps
#7
execOrder
#8
execFwdPositionOpsV2
#9
setData
#10
0x93697c…6cd4
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x6527b0cd…3c03
0x34b655…2a6f
2 touches
0 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
2 touches
0 conflicts
0xaefce33c…71c0
0x34b655…2a6f
2 touches
0 conflicts
0xb543d97e…cc3f
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity