pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,778,004
← previous block
next block →
recent activity
Analyzing
Block #85,778,004
11 transactions · 7 stateful · 2026-07-05 14:24:41 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,778,004
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xed82b078
#3
0x6a4a69a1
#4
transfer
#5
setData
#6
0xf36a4f…ceea
#7
0xb8eedc…1d22
#8
execOrders
· blocks 1
#9
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0382fe33…4c5f
0x34b655…2a6f
4 touches
1 conflict
0x09676f50…923f
0x065c9d…c394
2 touches
0 conflicts
0x0d854869…4f28
0x065c9d…c394
2 touches
0 conflicts
0x26b068a6…2960
0x065c9d…c394
2 touches
0 conflicts
0x30b68c43…9cc7
0x065c9d…c394
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
0x070a562acf…648147
Audit this contract →
← previous block
·
next block →
recent activity