pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,327,390
← previous block
next block →
recent activity
Analyzing
Block #98,327,390
13 transactions · 11 stateful · 2026-08-22 23:46:09 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
#98,327,390
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x7b84f330
#3
execOrders
#4
execOrders
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
0x5acec890
· blocks 1
#9
executeBatch
#11
setData
#12
execOrders
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b16dd0…0426
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0007
0x340143…768f
2 touches
0 conflicts
0x0217672a…90ed
0x34b655…2a6f
2 touches
0 conflicts
0x10c2ec3c…cd0c
0x34b655…2a6f
2 touches
0 conflicts
0x23361cbc…b058
0x34b655…2a6f
2 touches
0 conflicts
0x272e5bd6…252d
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
0xb7b16dd022…c80426
Audit this contract →
← previous block
·
next block →
recent activity