pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,515,777
← previous block
next block →
recent activity
Analyzing
Block #85,515,777
9 transactions · 6 stateful · 2026-07-04 09:17:25 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,515,777
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6a48d01d
#3
setData
#4
0x32366535
#5
0x6ac270…b448
#6
0x39435dac
· blocks 1
#8
0x39435dac
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa949fc8…c7ea
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x07ea30d9…c4c1
0x34b655…2a6f
2 touches
0 conflicts
0x62717024…ac25
0x34b655…2a6f
2 touches
0 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
2 touches
0 conflicts
0x85eb1316…bb9e
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
0xaa949fc84a…62c7ea
Audit this contract →
← previous block
·
next block →
recent activity