pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,598,539
← previous block
next block →
recent activity
Analyzing
Block #84,598,539
10 transactions · 7 stateful · 2026-06-30 03:23:05 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,598,539
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
0x39435dac
· blocks 1
#6
0x0f6795d9
#7
setData
#8
0x5ee63c…f02e
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44d5376…33cc
0x34b655…2a6f
4 touches
1 conflict
0xd5c5d2a2…99d5
0x34b655…2a6f
4 touches
1 conflict
0x97fe3267…5e87
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
2 touches
0 conflicts
0x1ca5aec6…c1e1
0x34b655…2a6f
2 touches
0 conflicts
0x2bedbb62…a662
0x34b655…2a6f
2 touches
0 conflicts
0x482b0aa9…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x602abf7f…b945
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
0xb44d5376ca…0b33cc
Audit this contract →
← previous block
·
next block →
recent activity