pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,703,608
← previous block
next block →
recent activity
Analyzing
Block #82,703,608
15 transactions · 13 stateful · 2026-06-21 08:37:04 UTC
Parallelism
80
/100
Blocked
15
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,703,608
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
withdraw
#3
0x6df9e92b
#4
0x5a5d9a99
#5
poke
#6
poke
#7
updateDataFeedsValuesPartial
#8
forward
#9
forward
#10
transfer
· blocks 2
#13
setData
#14
0x39435dac
#11
transfer
· blocks 1
#12
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0xe719b8f1…af6b
0x000000…012a
2 touches
0 conflicts
0xb52c5dc1…99db
0x065c9d…c394
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
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:
USDC (USDC)
3 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity