pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,730,653
← previous block
next block →
recent activity
Analyzing
Block #84,730,653
10 transactions · 10 stateful · 2026-06-30 18:03:24 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,730,653
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x39435dac
· blocks 2
#4
updateDataFeedsValuesPartial
#6
0x6a440563
#7
setData
#8
0x39435dac
#9
0x39435dac
#3
0x39435dac
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d691210…341b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x02134277…3124
0x34b655…2a6f
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x516f6141…f41a
0x34b655…2a6f
4 touches
1 conflict
0x6ddc5a74…5ec2
0x34b655…2a6f
4 touches
1 conflict
0x7075af84…8afb
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x8d69121037…43341b
Audit this contract →
← previous block
·
next block →
recent activity