pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,785,049
← previous block
next block →
recent activity
Analyzing
Block #85,785,049
9 transactions · 7 stateful · 2026-07-05 15:11:41 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,785,049
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x6a4a74a5
#6
0x6a4a74a5
#7
setData
#8
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cda3f80…809b
0x34b655…2a6f
4 touches
1 conflict
0x94de392a…e07a
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x1c1f68e0…d1aa
0x34b655…2a6f
3 touches
1 conflict
0x29638799…189e
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x0778475b…bd75
0x2a68ba…90c5
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
0x6cda3f8094…c4809b
Audit this contract →
← previous block
·
next block →
recent activity