pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,160,597
← previous block
next block →
recent activity
Analyzing
Block #85,160,597
11 transactions · 11 stateful · 2026-07-02 17:52:05 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,160,597
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x5a5d9a99
#3
0x9e76c652
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a46a5bc
#7
setData
#8
0x39435dac
· blocks 1
#10
0xc7e3ec2c
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00ca5a7d…debb
0x34b655…2a6f
2 touches
0 conflicts
0x03a55247…abfe
0x34b655…2a6f
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x118b8db9…9f73
0x34b655…2a6f
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity