pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,059,592
← previous block
next block →
recent activity
Analyzing
Block #84,059,592
12 transactions · 8 stateful · 2026-06-27 15:31:12 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,059,592
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#5
0x0c7abd22
#6
forward
#7
0xed82b078
#9
setData
#10
0x36326531
#11
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
4 touches
1 conflict
0xbb7fe6ca…b713
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xae69e878…7aab
0x34b655…2a6f
3 touches
1 conflict
0xc17614fa…6505
0x34b655…2a6f
3 touches
1 conflict
0x3eba034d…b7e8
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
0xb99958f6c8…c6ccf0
Audit this contract →
← previous block
·
next block →
recent activity