pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,966,479
← previous block
next block →
recent activity
Analyzing
Block #85,966,479
9 transactions · 8 stateful · 2026-07-06 11:20:38 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,966,479
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0xaf47a8bb
#5
setData
#6
0x0f6795d9
· blocks 1
#8
0x6a4b8ffe
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x6819a8f2…4392
0x34b655…2a6f
3 touches
1 conflict
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
2 touches
0 conflicts
0x4eb758b8…b13b
0x3bd359…433a
2 touches
0 conflicts
0x67d846dd…358c
0x3f86ce…7777
2 touches
0 conflicts
0x9e631f4f…8752
0x3f86ce…7777
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
0xe06bbb2ef5…889417
Audit this contract →
← previous block
·
next block →
recent activity