pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,706,456
← previous block
next block →
recent activity
Analyzing
Block #85,706,456
12 transactions · 11 stateful · 2026-07-05 06:28:30 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,706,456
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
0x5bf9264c
#7
0x5bf9264c
#8
0x0f6795d9
· blocks 1
#10
0x3f5c179b
#11
setData
#9
0x0f6795d9
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
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x02991b41…19e6
0x34b655…2a6f
2 touches
0 conflicts
0x10425555…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0x2382a4de…a921
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
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
0xafd867b7ed…d92b2e
Audit this contract →
← previous block
·
next block →
recent activity