pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,645,117
← previous block
next block →
recent activity
Analyzing
Block #85,645,117
10 transactions · 10 stateful · 2026-07-04 23:38:43 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,645,117
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x6a4999fa
#8
setData
#9
0x5d2fd812
#2
0x39ecce49
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x551f6273…7c20
0x42a4aa…7777
4 touches
1 conflict
0x00000000…0000
0x37b81d…17d7
4 touches
1 conflict
0x00000000…0001
0x37b81d…17d7
4 touches
1 conflict
0x00000000…0003
0x37b81d…17d7
4 touches
1 conflict
0x3b23d356…dcda
0x3bd359…433a
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xd70bb8d8…c9ca
0x42a4aa…7777
2 touches
0 conflicts
0xff1435f6…342f
0x42a4aa…7777
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:
0x42a4aa89…3d7777
1 conflict on slot
0x551f6273ab…8d7c20
Audit this contract →
← previous block
·
next block →
recent activity