pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,876,685
← previous block
next block →
recent activity
Analyzing
Block #90,876,685
8 transactions · 8 stateful · 2026-07-27 21:16:41 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,876,685
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
setData
#4
execFwdPositionOps
· blocks 1
#6
execOrders
#7
approve
#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
0xc1feb214…9967
0x34b655…2a6f
4 touches
1 conflict
0x80656e3b…9240
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00e2cc9a…61e3
0x34b655…2a6f
2 touches
0 conflicts
0x050948a5…a3f4
0x34b655…2a6f
2 touches
0 conflicts
0x0ea92501…8fe3
0x34b655…2a6f
2 touches
0 conflicts
0x12f58c96…4ef5
0x34b655…2a6f
2 touches
0 conflicts
0x24eaf46d…8c2e
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
0xc1feb2142f…0c9967
Audit this contract →
← previous block
·
next block →
recent activity