pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,356,732
← previous block
next block →
recent activity
Analyzing
Block #92,356,732
10 transactions · 8 stateful · 2026-08-02 01:25:02 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,356,732
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 2
#4
executeBatch
#7
execOrders
#8
0x6a6e9ce6
#9
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1a69c7c5…09cc
0x34b655…2a6f
4 touches
1 conflict
0x5827be1e…2a9f
0x34b655…2a6f
4 touches
1 conflict
0x9ddd4f34…0588
0x34b655…2a6f
2 touches
0 conflicts
0x9ddd4f34…0589
0x34b655…2a6f
2 touches
0 conflicts
0xfd380161…16e6
0x67d1be…196f
2 touches
0 conflicts
0x22c240c6…d7d0
0xd42a27…01c7
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
3 conflicts on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity