pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,625,019
← previous block
next block →
recent activity
Analyzing
Block #85,625,019
8 transactions · 7 stateful · 2026-07-04 21:24:52 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,625,019
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
· blocks 1
#5
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e1faa73…bfbf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x162f5e54…ef30
0x34b655…2a6f
2 touches
0 conflicts
0x398c3a27…6f7e
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
0x34b655…2a6f
2 touches
0 conflicts
0x7d967903…aef7
0x34b655…2a6f
2 touches
0 conflicts
0x7d967903…aef8
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
0x7e1faa73db…84bfbf
Audit this contract →
← previous block
·
next block →
recent activity