pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,805,489
← previous block
next block →
recent activity
Analyzing
Block #85,805,489
9 transactions · 8 stateful · 2026-07-05 17:27:55 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,805,489
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
0x6df9e92b
#7
setData
#8
0xe24fe7…33e2
#5
0x39435dac
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
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x8595db3e…c610
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
2 touches
0 conflicts
0x0d6d262c…958d
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
0x34b655…2a6f
2 touches
0 conflicts
0x84d74093…7808
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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…d92b2d
Audit this contract →
← previous block
·
next block →
recent activity