pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,638,662
← previous block
next block →
recent activity
Analyzing
Block #83,638,662
11 transactions · 10 stateful · 2026-06-25 16:44:14 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,638,662
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
executeBatch
#7
setData
#8
0x61633731
#10
0xc7e3ec2c
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0xada5add7…eb29
0x34b655…2a6f
4 touches
1 conflict
0xf7468e81…86e5
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x4fbf296b…b9ea
0x34b655…2a6f
2 touches
0 conflicts
0x5762e48b…3a85
0x34b655…2a6f
2 touches
0 conflicts
0x6652e56a…1c19
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
0x7fe9719817…9c79ab
Audit this contract →
← previous block
·
next block →
recent activity