pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,516,121
← previous block
next block →
recent activity
Analyzing
Block #84,516,121
10 transactions · 9 stateful · 2026-06-29 18:13:18 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,516,121
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6a42b635
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#5
0xed82b078
#7
setData
#9
0xc7e3ec2c
#6
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89ef0dba…31e2
0x34b655…2a6f
4 touches
1 conflict
0xbc8ead31…90fd
0x34b655…2a6f
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x241a8f3a…868d
0x34b655…2a6f
2 touches
0 conflicts
0x408e1b25…3f33
0x34b655…2a6f
2 touches
0 conflicts
0x52d7684e…db04
0x34b655…2a6f
2 touches
0 conflicts
0x55000eff…76a0
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
0x89ef0dba82…8331e2
Audit this contract →
← previous block
·
next block →
recent activity