pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,561,633
← previous block
next block →
recent activity
Analyzing
Block #89,561,633
11 transactions · 9 stateful · 2026-07-23 03:59:50 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,561,633
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x36bf8a…1b16
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
setData
#7
execFwdPositionOps
#8
batchUpdate
#9
0x6a61922e
#10
execOrders
#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
0x3acc628e…e425
0x34b655…2a6f
4 touches
1 conflict
0xff533a5f…685e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0a6ba3b4…2123
0x34b655…2a6f
2 touches
0 conflicts
0x13f654fc…8882
0x34b655…2a6f
2 touches
0 conflicts
0x322fb0e8…962d
0x34b655…2a6f
2 touches
0 conflicts
0x5866aa50…fe80
0x34b655…2a6f
2 touches
0 conflicts
0x5866aa50…fe81
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
0x3acc628ef6…57e425
Audit this contract →
← previous block
·
next block →
recent activity