pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,268,879
← previous block
next block →
recent activity
Analyzing
Block #82,268,879
10 transactions · 8 stateful · 2026-06-19 08:13:14 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,268,879
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#3
0x23afbff3
#4
updateDataFeedsValuesPartial
#5
execute
#6
exactInputSingle
#7
setData
#8
0x252adb…5783
#9
0x39435dac
#2
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc04078c2…5362
0x34b655…2a6f
4 touches
1 conflict
0xcc3f7ee8…7924
0x34b655…2a6f
4 touches
1 conflict
0xf09731bc…a7b2
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x60c7217a…8c94
0x34b655…2a6f
4 touches
1 conflict
0x6b9f48fc…8364
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
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
0xc04078c27b…b75362
Audit this contract →
← previous block
·
next block →
recent activity