pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,638,130
← previous block
next block →
recent activity
Analyzing
Block #83,638,130
11 transactions · 8 stateful · 2026-06-25 16:40:42 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,638,130
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
updatePrices
#5
0x5a5d9a99
· blocks 1
#7
0x0f6795d9
#8
0x0c7abd22
#9
forward
#10
setData
#6
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b408000…9df1
0x34b655…2a6f
2 touches
0 conflicts
0x0cfbafcc…45a5
0x34b655…2a6f
2 touches
0 conflicts
0x3390d751…4f99
0x34b655…2a6f
2 touches
0 conflicts
0x67a0f456…07e7
0x34b655…2a6f
2 touches
0 conflicts
0x7500c6c7…6b90
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
0xe99d8e683a…2ea16e
Audit this contract →
← previous block
·
next block →
recent activity