pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,574,126
← previous block
next block →
recent activity
Analyzing
Block #92,574,126
10 transactions · 9 stateful · 2026-08-02 19:38:21 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
#92,574,126
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
execFwdPositionOps
· blocks 1
#6
0x6a6f9d25
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x6323c5ea…ce8a
0x34b655…2a6f
2 touches
0 conflicts
0x7d6e48e8…f2b5
0x34b655…2a6f
2 touches
0 conflicts
0x8b87ece6…3353
0x34b655…2a6f
2 touches
0 conflicts
0xc3a8e1d6…e816
0x34b655…2a6f
2 touches
0 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity