pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,917,422
← previous block
next block →
recent activity
Analyzing
Block #85,917,422
9 transactions · 6 stateful · 2026-07-06 05:53:24 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,917,422
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#7
setData
#8
0x666b4f…5059
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0x7a4dccb5…d2fb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0ec96631…b0f1
0x34b655…2a6f
2 touches
0 conflicts
0x0ff91e5e…6434
0x34b655…2a6f
2 touches
0 conflicts
0x1cefae97…7f45
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
0x3a6290da4d…93e683
Audit this contract →
← previous block
·
next block →
recent activity