pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,236,504
← previous block
next block →
recent activity
Analyzing
Block #92,236,504
11 transactions · 10 stateful · 2026-08-01 15:20:21 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,236,504
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
execFwdPositionOps
#9
setData
#10
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x09c0f2d7…bb37
0x34b655…2a6f
2 touches
0 conflicts
0x0cbfe623…1409
0x34b655…2a6f
2 touches
0 conflicts
0x15b254ac…664f
0x34b655…2a6f
2 touches
0 conflicts
0x1a843f41…02aa
0x34b655…2a6f
2 touches
0 conflicts
0x25352d3e…4ec7
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
0x29c1a140f5…fc099f
Audit this contract →
← previous block
·
next block →
recent activity