pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,594,929
← previous block
next block →
recent activity
Analyzing
Block #85,594,929
8 transactions · 6 stateful · 2026-07-04 18:04:35 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,594,929
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x3f5c179b
#4
updateDataFeedsValuesPartial
#5
0x6a494bab
#6
0x39435dac
#7
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0x4565f421…80b9
0x34b655…2a6f
4 touches
1 conflict
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdd28262d…59ef
0x34b655…2a6f
4 touches
1 conflict
0x09be8369…e9e7
0x34b655…2a6f
2 touches
0 conflicts
0x471fb752…394e
0x34b655…2a6f
2 touches
0 conflicts
0x810a3aa2…0227
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
0x745a7fd6fd…595fea
Audit this contract →
← previous block
·
next block →
recent activity