pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,767,257
← previous block
next block →
recent activity
Analyzing
Block #85,767,257
8 transactions · 7 stateful · 2026-07-05 13:13:12 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,767,257
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x3f5c179b
#4
0x6df9e92b
#5
setData
#6
0x766f00…70a0
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x261b18ac…d06d
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x1ee06932…8671
0x34b655…2a6f
2 touches
0 conflicts
0x2d93071a…5ba7
0x34b655…2a6f
2 touches
0 conflicts
0x4905be8a…073f
0x34b655…2a6f
2 touches
0 conflicts
0x4bd2fdc3…0d6d
0x34b655…2a6f
2 touches
0 conflicts
0x5a3e3430…7e44
0x34b655…2a6f
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
0x077d58c3dc…178ed7
Audit this contract →
← previous block
·
next block →
recent activity