pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,694,333
← previous block
next block →
recent activity
Analyzing
Block #82,694,333
11 transactions · 9 stateful · 2026-06-21 07:35:16 UTC
Parallelism
64
/100
Blocked
33
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,694,333
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5339c59f
#2
0x5339c59f
#3
0xfc8ff304
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
transfer
· blocks 3
#10
setData
#7
transfer
· blocks 2
#8
transfer
· blocks 1
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
9
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0xc6e07193…759a
0x000000…012a
2 touches
0 conflicts
0x11404a00…dd12
0x065c9d…c394
2 touches
0 conflicts
0x769f6332…5dd4
0x065c9d…c394
2 touches
0 conflicts
0x8fee2109…b7c5
0x065c9d…c394
2 touches
0 conflicts
0xa8a2ebb3…b23f
0x065c9d…c394
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)
6 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity