pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,250,243
← previous block
next block →
recent activity
Analyzing
Block #85,250,243
8 transactions · 7 stateful · 2026-07-03 03:49:11 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,250,243
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
executeBatch
#7
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95847041…2d63
0x34b655…2a6f
4 touches
1 conflict
0x9c961d69…6727
0x34b655…2a6f
4 touches
1 conflict
0xc5d8cc36…cbf8
0x34b655…2a6f
4 touches
1 conflict
0x30153288…6d46
0x34b655…2a6f
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x83f3d320…fb59
0x34b655…2a6f
2 touches
0 conflicts
0x8d24fe06…31f4
0x34b655…2a6f
2 touches
0 conflicts
0x90f280af…d845
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
0x95847041f0…322d63
Audit this contract →
← previous block
·
next block →
recent activity