pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,372,574
← previous block
next block →
recent activity
Analyzing
Block #85,372,574
8 transactions · 7 stateful · 2026-07-03 17:24:02 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,372,574
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#6
setData
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd8d502…d359
0x34b655…2a6f
4 touches
1 conflict
0xb75d9839…c7bd
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x284bb696…4091
0x34b655…2a6f
2 touches
0 conflicts
0x4f307542…6d77
0x34b655…2a6f
2 touches
0 conflicts
0x5f34fd08…aeb3
0x34b655…2a6f
2 touches
0 conflicts
0x89999c15…fdac
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
0xafd8d502ad…46d359
Audit this contract →
← previous block
·
next block →
recent activity