pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,262,298
← previous block
next block →
recent activity
Analyzing
Block #96,262,298
8 transactions · 8 stateful · 2026-08-15 17:24:05 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,262,298
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
#5
setData
#6
0x61d59c2d
· blocks 1
#7
swapExactTokensForTokens
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf3
0x77d53b…8080
4 touches
1 conflict
0xf101bd5c…0dc7
0x77d53b…8080
4 touches
1 conflict
0x14a9d879…fbf5
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x282ee211…9c06
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c6f
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:
0x77d53b3b…378080
1 conflict on slot
0x0fd2cbc574…1c476b
Audit this contract →
← previous block
·
next block →
recent activity