pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,571,357
← previous block
next block →
recent activity
Analyzing
Block #84,571,357
9 transactions · 8 stateful · 2026-06-30 00:22:03 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,571,357
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 1
#3
relay
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b111712…0e59
0x34b655…2a6f
4 touches
1 conflict
0xceb535f3…19cf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x26918bca…6c75
0x34b655…2a6f
4 touches
1 conflict
0x0aa5b76b…60db
0x34b655…2a6f
2 touches
0 conflicts
0x0e0b2b28…3948
0x34b655…2a6f
2 touches
0 conflicts
0x1efeb70c…9a8c
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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
0x2b1117126f…080e59
Audit this contract →
← previous block
·
next block →
recent activity