pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,984,159
← previous block
next block →
recent activity
Analyzing
Block #85,984,159
9 transactions · 7 stateful · 2026-07-06 13:18: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,984,159
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
#3
0x0f6795d9
#4
0xed82b078
#5
0x6a4baba9
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50887223…db7f
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0xd90a674b…29f7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa500b57d…dad8
0x34b655…2a6f
4 touches
1 conflict
0xbf043a30…5829
0x34b655…2a6f
4 touches
1 conflict
0x343e2fac…0ace
0x34b655…2a6f
2 touches
0 conflicts
0x3b6e959d…158f
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
0x508872232f…04db7f
Audit this contract →
← previous block
·
next block →
recent activity