pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,490,819
← previous block
next block →
recent activity
Analyzing
Block #84,490,819
10 transactions · 8 stateful · 2026-06-29 15:24:24 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,490,819
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x85367786
#7
updateDataFeedsValuesPartial
#8
setData
#9
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75cdffd8…c217
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x92bc052c…c2ff
0x34b655…2a6f
4 touches
1 conflict
0x97943d6f…71b5
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x344dbdb0…0cc0
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
0x75cdffd8c9…dec217
Audit this contract →
← previous block
·
next block →
recent activity