pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,278,586
← previous block
next block →
recent activity
Analyzing
Block #84,278,586
11 transactions · 11 stateful · 2026-06-28 15:49:44 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,278,586
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addLiquidityNATIVE
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
execFwdPositionOps
· blocks 2
#6
execFwdPositionOps
#7
execFwdPositionOps
#9
setData
#8
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb7f0577…02bc
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xc43aefda…e47d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xb6b7c45d…9d5a
0x34b655…2a6f
4 touches
1 conflict
0x828cefbb…7934
0x34b655…2a6f
3 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
1 conflict on slot
0xeb7f0577e2…c102bc
Audit this contract →
← previous block
·
next block →
recent activity