pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,671,545
← previous block
next block →
recent activity
Analyzing
Block #85,671,545
10 transactions · 8 stateful · 2026-07-05 02:34:37 UTC
Parallelism
60
/100
Blocked
38
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,671,545
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#5
0x1094dc9f
#6
updateDataFeedsValuesPartial
#7
0x6a49c335
#8
setData
#9
0x39435dac
#2
0x0c7abd22
· blocks 2
#3
0x0c7abd22
· blocks 1
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a639673…daf3
0xd32edf…ff58
7 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0001
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0003
0x019883…2a9a
2 touches
0 conflicts
0x00000000…000f
0x019883…2a9a
2 touches
0 conflicts
0x04a63e8d…bf5d
0x0cc9b2…7777
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:
FastLane: FastLaneAuctionHandler
6 conflicts on slot
0x7a639673f8…ffdaf3
Audit this contract →
← previous block
·
next block →
recent activity