pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,185,700
← previous block
next block →
recent activity
Analyzing
Block #97,185,700
13 transactions · 13 stateful · 2026-08-18 23:01:39 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,185,700
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
· blocks 1
#4
execOrders
#5
updatePrices
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#9
execOrders
#10
setData
#11
execOrders
· blocks 1
#3
matchOrders
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
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
0x15c6ded9…48e7
0x754704…b603
4 touches
1 conflict
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
0xd4c946a4…b8d4
0x754704…b603
4 touches
1 conflict
0x45436af6…437f
0x99c7a7…8bf0
4 touches
1 conflict
0x66300207…c47a
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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