pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,909,333
← previous block
next block →
recent activity
Analyzing
Block #85,909,333
13 transactions · 9 stateful · 2026-07-06 04:59:33 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,909,333
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
· blocks 1
#3
0xaf5e395a
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
#6
0xccf50a51
#7
0x62be7533
#8
0x0f6795d9
#9
0xc1f789…e3f7
#10
0x6ea0d1…9801
#11
setData
#12
0xc7e3ec2c
#2
0x1094dc9f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0xe90b7bce…c2e0
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0003
0x094452…0a09
2 touches
0 conflicts
0x00000000…0004
0x094452…0a09
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:
Wrapped MON (WMON)
1 conflict on slot
0x99f666e3cf…76b2a2
Audit this contract →
← previous block
·
next block →
recent activity