pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,350,648
← previous block
next block →
recent activity
Analyzing
Block #84,350,648
11 transactions · 10 stateful · 2026-06-28 23:49:54 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,350,648
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x6a41b39a
#4
execFwdPositionOps
· blocks 2
#5
executeBatch
#6
0x0c7abd22
#7
0xed82b078
#9
setData
#8
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x3ec82b22…1f46
0x34b655…2a6f
4 touches
1 conflict
0x1d55e141…7d5b
0x34b655…2a6f
2 touches
0 conflicts
0x956a31c2…e520
0x34b655…2a6f
2 touches
0 conflicts
0xd2274a53…9d6a
0x34b655…2a6f
2 touches
0 conflicts
0xd52269a0…d7c9
0x34b655…2a6f
2 touches
0 conflicts
0xe334a6b5…173c
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
0x6f132c01d5…7dcdcc
Audit this contract →
← previous block
·
next block →
recent activity