pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,443,403
← previous block
next block →
recent activity
Analyzing
Block #87,443,403
11 transactions · 9 stateful · 2026-07-13 07:52:22 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,443,403
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
· blocks 1
#7
execFwdPositionOps
· blocks 1
#9
setData
#10
execOrders
#6
batchUpdate
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x216a925b…4353
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb0ba1e07…e059
0xa6afd3…d132
4 touches
1 conflict
0x06fbff00…d58a
0xa6afd3…d132
3 touches
1 conflict
0x590b0737…23c7
0xa6afd3…d132
3 touches
1 conflict
0x1896e05f…0421
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x37c1a18b…0cd1
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
0x216a925bc0…254353
Audit this contract →
← previous block
·
next block →
recent activity