pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,027,906
← previous block
next block →
recent activity
Analyzing
Block #84,027,906
12 transactions · 10 stateful · 2026-06-27 12:00:05 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,027,906
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
exactInputSingle
#3
0x9e76c652
#4
0xed82b078
#5
0x0f6795d9
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a3fbbbd
#8
0xe9316489
#9
0xe9316489
#10
setData
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x05b8ccbb…46bc
0x2ab50b…5c41
2 touches
0 conflicts
0x06d60e39…4ebd
0x2ab50b…5c41
2 touches
0 conflicts
0x0b8e6fa6…19e0
0x2ab50b…5c41
2 touches
0 conflicts
0x218634ca…d736
0x2ab50b…5c41
2 touches
0 conflicts
0x292e40ff…05e2
0x2ab50b…5c41
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity