pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,251,947
← previous block
next block →
recent activity
Analyzing
Block #80,251,947
12 transactions · 8 stateful · 2026-06-10 00:08:29 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,251,947
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3f5c179b
#2
updateDataFeedsValuesPartial
#3
exactInputSingle
#4
updateDataFeedsValuesPartial
#5
transfer
#6
setData
#7
0xac603b…abb2
#8
0x947df0…5459
#9
0x43a54c…71cb
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x24b18e…3301
2 touches
0 conflicts
0x00000000…0001
0x24b18e…3301
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x771a3650…01cd
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
2 touches
0 conflicts
0xa743c8dd…ebf2
0x788571…8888
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
0x2aab08973a…f178f7
Audit this contract →
← previous block
·
next block →
recent activity