pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,745,740
← previous block
next block →
recent activity
Analyzing
Block #85,745,740
10 transactions · 6 stateful · 2026-07-05 10:49:59 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,745,740
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
execFwdPositionOps
· blocks 1
#4
batchUpdate
#6
0x6a4a374f
#7
0xa6fc17…4e91
#8
0xc7e937…3aa1
#9
0x90e3a9…4d5d
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x061eb968…67af
0x065c9d…c394
2 touches
0 conflicts
0x35f470c6…d7c0
0x065c9d…c394
2 touches
0 conflicts
0x4533cc44…b192
0x065c9d…c394
2 touches
0 conflicts
0x547efef1…f85f
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
0xa20a130ca6…b85d59
Audit this contract →
← previous block
·
next block →
recent activity