pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,728,976
← previous block
next block →
recent activity
Analyzing
Block #82,728,976
10 transactions · 8 stateful · 2026-06-21 11:26:26 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
#82,728,976
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
· blocks 1
#5
executeBatch
#6
forward
#7
0x6a37cada
#8
setData
#9
0x39435dac
#4
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb665ffc5…d222
0xc8689a…ee79
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x1a7e1844…4b4c
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x9cd33a29…fef8
0x34b655…2a6f
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
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: Settlement / Helper
1 conflict on slot
0xb665ffc58f…2ad222
Audit this contract →
← previous block
·
next block →
recent activity