pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,169,055
← previous block
next block →
recent activity
Analyzing
Block #85,169,055
9 transactions · 8 stateful · 2026-07-02 18:48:22 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,169,055
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
· blocks 2
#6
0x3f5c179b
#7
setData
#8
0x39435dac
#4
0x5a5d9a99
· blocks 1
#5
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0xa1144aa9…7f67
0x34b655…2a6f
4 touches
1 conflict
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0xb7ce2911…aa51
0x34b655…2a6f
4 touches
1 conflict
0xe0d1507c…c95e
0x34b655…2a6f
4 touches
1 conflict
0xebd8c9b0…2ba6
0x34b655…2a6f
4 touches
1 conflict
0x16b3a441…13db
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xfaef08b108…f90696
Audit this contract →
← previous block
·
next block →
recent activity