pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,099,518
← previous block
next block →
recent activity
Analyzing
Block #84,099,518
10 transactions · 9 stateful · 2026-06-27 19:57:12 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,099,518
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
updatePrices
#4
0x0f6795d9
· blocks 1
#5
executeBatch
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3464aef1…176f
0x065c9d…c394
2 touches
0 conflicts
0x393a54ef…e6bd
0x065c9d…c394
2 touches
0 conflicts
0x4e7e9883…a07f
0x065c9d…c394
2 touches
0 conflicts
0x8f45c92c…de8a
0x065c9d…c394
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
0xd58b9a66f8…5f1c23
Audit this contract →
← previous block
·
next block →
recent activity