pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,744,829
← previous block
next block →
recent activity
Analyzing
Block #85,744,829
12 transactions · 8 stateful · 2026-07-05 10:43:58 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,744,829
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
0x6c05cd2b
#6
0x62be7533
#7
0x0f6795d9
· blocks 1
#8
0x6a4a35e6
#9
setData
#10
0xb8044e36
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x2fb6ddd2…b2a4
0x000000…012a
2 touches
0 conflicts
0x66cef849…fdcc
0x000000…012a
2 touches
0 conflicts
0x3a1e6958…6dc3
0x188d58…ea8e
2 touches
0 conflicts
0x3a1e6958…6dc5
0x188d58…ea8e
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity