pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,504,619
← previous block
next block →
recent activity
Analyzing
Block #85,504,619
14 transactions · 11 stateful · 2026-07-04 08:03:14 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,504,619
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x05ee6a22
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
0x5a5d9a99
#6
0x62be7533
#7
0x0c7abd22
#8
0x204ce421
· blocks 1
#10
setData
#11
0x6bdec372
#12
0xc7e3ec2c
#13
0xc7e3ec2c
#9
0x204ce421
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0014
0x2f55a2…8375
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x9cafc3b6…ee8c
0x000000…012a
2 touches
0 conflicts
0x457f87c7…30ca
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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:
0x2f55a2e1…f48375
1 conflict on slot
0x0000000000…000014
Audit this contract →
← previous block
·
next block →
recent activity