pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,625,514
← previous block
next block →
recent activity
Analyzing
Block #83,625,514
15 transactions · 12 stateful · 2026-06-25 15:16:21 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,625,514
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
deposit
#9
0x0c7abd22
#10
forward
#11
0x0f6795d9
#12
exactInputSingle
#13
setData
#14
0xc7e3ec2c
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x0c65a0…0852
2 touches
0 conflicts
0xb1acfe51…c6b1
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0002
0x63e48b…53f2
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:
0xaa7ee7ce…aff0e4
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity