pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,379,819
← previous block
next block →
recent activity
Analyzing
Block #98,379,819
11 transactions · 10 stateful · 2026-08-23 04:09:54 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,379,819
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
0xab083028
#4
0xab083028
#5
execOrder
· blocks 1
#6
0x59558d29
#9
setData
#10
execOrders
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfef7b992…e091
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x1cc32af8…dcc2
0x34b655…2a6f
4 touches
1 conflict
0x5934b407…e058
0x34b655…2a6f
4 touches
1 conflict
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
0xbaf77397f3…58e798
Audit this contract →
← previous block
·
next block →
recent activity