pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,430,140
← previous block
next block →
recent activity
Analyzing
Block #97,430,140
10 transactions · 9 stateful · 2026-08-19 20:03:07 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,430,140
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x6ad2e98b
#3
0xa96df62f
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
0x57368ddf
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x24a3b302…75bb
0x34b655…2a6f
2 touches
0 conflicts
0x342ec28c…cd7f
0x34b655…2a6f
2 touches
0 conflicts
0x35ea602c…019a
0x34b655…2a6f
2 touches
0 conflicts
0x3dcf86fa…a98d
0x34b655…2a6f
2 touches
0 conflicts
0x4d0e3f2f…3696
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity