pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,594,746
← previous block
next block →
recent activity
Analyzing
Block #85,594,746
10 transactions · 9 stateful · 2026-07-04 18:03:22 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,594,746
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#4
0x0f6795d9
#5
0x3f5c179b
#8
setData
#6
0x3f5c179b
#7
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
6
w1
7
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0a370f34…31b9
0x34b655…2a6f
4 touches
1 conflict
0x17c44db3…8888
0xa6afd3…d132
4 touches
1 conflict
0xbcc5ae85…6ba2
0xa6afd3…d132
4 touches
1 conflict
0x08d66073…e706
0x34b655…2a6f
2 touches
0 conflicts
0x34518ce2…7a66
0x34b655…2a6f
2 touches
0 conflicts
0x72fd59f1…b722
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
3 conflicts on slot
0xc0eb79d1cb…5529a4
Audit this contract →
← previous block
·
next block →
recent activity