pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,139,890
← previous block
next block →
recent activity
Analyzing
Block #85,139,890
11 transactions · 10 stateful · 2026-07-02 15:34:12 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,139,890
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
execPerpOps
#4
execPerpOps
#5
0x5a5d9a99
· blocks 2
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#6
0x5a5d9a99
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xa0efa7bc…8b24
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
0x34b655…2a6f
4 touches
1 conflict
0xc83310b1…c778
0x34b655…2a6f
4 touches
1 conflict
0xc99e7125…81b1
0x34b655…2a6f
4 touches
1 conflict
0xca52f970…195c
0x34b655…2a6f
4 touches
1 conflict
0xe47478a3…a058
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xfaef08b108…f90696
Audit this contract →
← previous block
·
next block →
recent activity