pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,621,813
← previous block
next block →
recent activity
Analyzing
Block #84,621,813
7 transactions · 6 stateful · 2026-06-30 05:58:09 UTC
Parallelism
71
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,621,813
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5bf9264c
· blocks 1
#4
0x0f6795d9
· blocks 1
#6
setData
#3
0x5bf9264c
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49194594…2c70
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x67fc285e…2584
0x34b655…2a6f
2 touches
0 conflicts
0x6adf1524…1768
0x34b655…2a6f
2 touches
0 conflicts
0x723d3210…b4e2
0x34b655…2a6f
2 touches
0 conflicts
0x97d5efed…1aa4
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
0x4919459402…d42c70
Audit this contract →
← previous block
·
next block →
recent activity