pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,659,804
← previous block
next block →
recent activity
Analyzing
Block #85,659,804
9 transactions · 6 stateful · 2026-07-05 01:16:24 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,659,804
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 2
#4
0x5bf9264c
#5
0x5bf9264c
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#8
setData
#2
0xab083028
· blocks 1
#3
0x6ad2e98b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x40064590…dbd6
0x40c49f…2af0
2 touches
0 conflicts
0xc13ed11e…5dd7
0x40c49f…2af0
2 touches
0 conflicts
0xe181a6d1…a267
0x40c49f…2af0
2 touches
0 conflicts
0xfdfc2fb3…9f2f
0x40c49f…2af0
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity