pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,766,511
← previous block
next block →
recent activity
Analyzing
Block #85,766,511
11 transactions · 9 stateful · 2026-07-05 13:08:14 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,766,511
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
aggregate3
#5
0x0f6795d9
· blocks 1
#6
updatePosition
#7
setData
#8
0x75c75d…b5e3
#10
0xc7e3ec2c
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c962d08…9e24
0x34b655…2a6f
4 touches
1 conflict
0x38d0f220…01f4
0x34b655…2a6f
4 touches
1 conflict
0x6bc87970…02de
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x259e08ee…0dcf
0x065c9d…c394
2 touches
0 conflicts
0x4e3e0bc7…44fb
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
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
0x8c962d0879…cd9e24
Audit this contract →
← previous block
·
next block →
recent activity