pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,910,027
← previous block
next block →
recent activity
Analyzing
Block #85,910,027
11 transactions · 9 stateful · 2026-07-06 05:04:11 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,910,027
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
updatePrices
#4
0x0f6795d9
#5
0x0f6795d9
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x19cf0c…a054
#10
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x104ecede…a3c3
0x065c9d…c394
2 touches
0 conflicts
0x1595ab7a…cbe9
0x065c9d…c394
2 touches
0 conflicts
0x25b5f017…564a
0x065c9d…c394
2 touches
0 conflicts
0x36f738b1…4d8b
0x065c9d…c394
2 touches
0 conflicts
0x6d8f609e…0554
0x065c9d…c394
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
0x1aaf499609…4665ec
Audit this contract →
← previous block
·
next block →
recent activity