pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,960,256
← previous block
next block →
recent activity
Analyzing
Block #92,960,256
12 transactions · 12 stateful · 2026-08-04 04:02:07 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,960,256
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
approve
#3
execFwdPositionOps
· blocks 1
#4
executeBatch
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
transfer
#11
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0xd6f5af80…92f3
0x34b655…2a6f
4 touches
1 conflict
0x4cb450ac…4047
0x34b655…2a6f
3 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
2 touches
0 conflicts
0x35b89cd8…5092
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x8765edd1…a7d5
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
0x31b3992285…921e66
Audit this contract →
← previous block
·
next block →
recent activity