pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,365,721
← previous block
next block →
recent activity
Analyzing
Block #85,365,721
9 transactions · 8 stateful · 2026-07-03 16:38:25 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,365,721
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x785f5745
#5
0xed82b078
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16698af3…267d
0x34b655…2a6f
4 touches
1 conflict
0x261c40aa…b133
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x989e45a7…74f8
0x0c65a0…0852
2 touches
0 conflicts
0x13d92ba0…8c20
0x34b655…2a6f
2 touches
0 conflicts
0x43e3decb…be40
0x34b655…2a6f
2 touches
0 conflicts
0xcef70a96…db44
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
0x16698af3e9…4b267d
Audit this contract →
← previous block
·
next block →
recent activity