pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,680,513
← previous block
next block →
recent activity
Analyzing
Block #85,680,513
11 transactions · 9 stateful · 2026-07-05 03:34:17 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,680,513
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x6c05cd2b
· blocks 1
#6
0x5339c59f
#7
0x6a49d131
#8
setData
#9
0xb8034e74
#10
0xc7e3ec2c
#5
0x6c05cd2b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe161dd…757b
0x3bd359…433a
4 touches
1 conflict
0xaee48438…cb1e
0x81a224…7777
4 touches
1 conflict
0xb4e825af…69e0
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0xd2448ab0…0253
0x3bd359…433a
2 touches
0 conflicts
0xf31a7ab8…327b
0x3bd359…433a
2 touches
0 conflicts
0x502545d8…29cc
0x503d19…1d74
2 touches
0 conflicts
0x00000000…0000
0x5674d1…021f
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:
Wrapped MON (WMON)
1 conflict on slot
0xfbe161dda4…a6757b
Audit this contract →
← previous block
·
next block →
recent activity