pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,937,907
← previous block
next block →
recent activity
Analyzing
Block #98,937,907
15 transactions · 14 stateful · 2026-08-25 03:34:13 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,937,907
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execOrder
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
0x3f5c179b
#7
batchUpdate
#8
0xed82b078
#9
0x39abec6b
#10
transferWithAuthorization
· blocks 1
#12
setData
#13
withdraw
#14
execOrders
#11
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2965e2d6…5800
0x34b655…2a6f
2 touches
0 conflicts
0x36a1f6ec…1e29
0x34b655…2a6f
2 touches
0 conflicts
0x41335ddf…94b9
0x34b655…2a6f
2 touches
0 conflicts
0x498b75ea…efad
0x34b655…2a6f
2 touches
0 conflicts
0x5095e01b…5cf0
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:
USDC (USDC)
1 conflict on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity