pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,853,712
← previous block
next block →
recent activity
Analyzing
Block #92,853,712
11 transactions · 10 stateful · 2026-08-03 19:06:02 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,853,712
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
executeBatch
#3
execFwdPositionOps
· blocks 1
#4
execOrders
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0xe9316489
#9
setData
#10
0x59558d29
#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
0x714420ba…96c5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca608d0c…f23b
0x34b655…2a6f
4 touches
1 conflict
0xd59b7c91…d1ef
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
2 touches
0 conflicts
0x5778d110…d2e6
0xc8689a…ee79
2 touches
0 conflicts
0x09e0690d…6e3d
0xe52b14…7230
2 touches
0 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
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
0x714420ba89…6d96c5
Audit this contract →
← previous block
·
next block →
recent activity