pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,617,937
← previous block
next block →
recent activity
Analyzing
Block #85,617,937
11 transactions · 9 stateful · 2026-07-04 20:37:45 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,617,937
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
forward
#7
updateDataFeedsValuesPartial
#8
0x6a496f91
#9
setData
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d7e60b7…c173
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x2fb80aae…a042
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x198aca5f…71f4
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x3c53a398…2be0
0x34b655…2a6f
2 touches
0 conflicts
0x66848050…644a
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
0x2d7e60b75a…fcc173
Audit this contract →
← previous block
·
next block →
recent activity