pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,940,305
← previous block
next block →
recent activity
Analyzing
Block #85,940,305
9 transactions · 7 stateful · 2026-07-06 08:26:01 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,940,305
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
multicall
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#6
setData
#7
0x26dce1…f9ca
#5
0x0f6795d9
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1a4179d3…0f26
0x068f22…7908
2 touches
0 conflicts
0x24104c4d…3a3a
0x068f22…7908
2 touches
0 conflicts
0x250efed1…5a09
0x068f22…7908
2 touches
0 conflicts
0x48dab8e7…787a
0x068f22…7908
2 touches
0 conflicts
0xaa5d1ec6…e2af
0x068f22…7908
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
3 conflicts on slot
0x1aaf499609…4665ec
Audit this contract →
← previous block
·
next block →
recent activity