pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,277,352
← previous block
next block →
recent activity
Analyzing
Block #84,277,352
8 transactions · 7 stateful · 2026-06-28 15:41:31 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,277,352
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
setData
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
0x6a414123
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1729ba3b…f91b
0x34b655…2a6f
4 touches
1 conflict
0xc9fe0433…7f01
0x34b655…2a6f
4 touches
1 conflict
0xe7d1113d…1493
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2a513dfb…2bb8
0x34b655…2a6f
4 touches
1 conflict
0x161b50ca…6816
0x34b655…2a6f
2 touches
0 conflicts
0x1b3ea27c…f376
0x34b655…2a6f
2 touches
0 conflicts
0x8eda4743…87e6
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
0x1729ba3b75…0af91b
Audit this contract →
← previous block
·
next block →
recent activity