pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,217,434
← previous block
next block →
recent activity
Analyzing
Block #98,217,434
13 transactions · 10 stateful · 2026-08-22 14:32:57 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,217,434
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x7b84f330
· blocks 1
#3
matchOrders
#4
0x59558d29
#5
execFwdPositionOpsV2
· blocks 1
#7
forward
#8
setData
#9
execOrders
#10
execOrders
#11
execOrders
#6
execFwdPositionOpsV2
#12
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
2 touches
0 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
2 touches
0 conflicts
0xc159cb1e…ef71
0x34b655…2a6f
2 touches
0 conflicts
0xc159cb1e…ef72
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
0x04994ed232…129032
Audit this contract →
← previous block
·
next block →
recent activity