pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,248,577
← previous block
next block →
recent activity
Analyzing
Block #84,248,577
11 transactions · 11 stateful · 2026-06-28 12:29:51 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,248,577
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
0x5a5d9a99
#3
0x0f6795d9
#4
0x0c7abd22
#5
exactInputSingle
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x2d59fc…cd50
4 touches
1 conflict
0x3f1434d4…1ce1
0x3bd359…433a
4 touches
1 conflict
0x3f1434d4…1ce1
0x11ed3b…2c96
4 touches
1 conflict
0x00000000…0000
0x2d59fc…cd50
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x5922589d…474d
0x34b655…2a6f
2 touches
0 conflicts
0x2dbc727c…778b
0x754704…b603
2 touches
0 conflicts
0xc07feb60…5e5f
0x754704…b603
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:
0x2d59fc33…60cd50
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity