pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,251,616
← previous block
next block →
recent activity
Analyzing
Block #84,251,616
10 transactions · 8 stateful · 2026-06-28 12:50:04 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,251,616
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a4118f4
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#6
0x9e76c652
#8
setData
#9
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9fc8ec77…2dee
0x34b655…2a6f
3 touches
1 conflict
0x2a4dbc20…1421
0x34b655…2a6f
3 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0a38d3dd…6397
0x34b655…2a6f
2 touches
0 conflicts
0x200db05e…6327
0x34b655…2a6f
2 touches
0 conflicts
0x201455cc…d6de
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
0x9a3068dd84…9918f1
Audit this contract →
← previous block
·
next block →
recent activity