pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,035,261
← previous block
next block →
recent activity
Analyzing
Block #84,035,261
9 transactions · 8 stateful · 2026-06-27 12:49:00 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,035,261
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x29eed2d3
#5
0xed82b078
#6
updateTemporalNumericValuesV1
#7
setData
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x23be01f1…9f7c
0x34b655…2a6f
2 touches
0 conflicts
0x24e133eb…b3c5
0x34b655…2a6f
2 touches
0 conflicts
0x264ceae9…73ba
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f0
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
0x07f6906240…ea03ec
Audit this contract →
← previous block
·
next block →
recent activity