pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,711,874
← previous block
next block →
recent activity
Analyzing
Block #85,711,874
10 transactions · 9 stateful · 2026-07-05 07:04:37 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,711,874
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x3f5c179b
#6
setData
#7
0x6a4a027d
#8
0x39435dac
#9
0xc7e3ec2c
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe27f60bf…62d9
0x065c9d…c394
4 touches
1 conflict
0xe7c75346…e34d
0x065c9d…c394
3 touches
1 conflict
0x045e64b9…7102
0x065c9d…c394
2 touches
0 conflicts
0x5603c879…da6c
0x065c9d…c394
2 touches
0 conflicts
0x62e66978…fc53
0x065c9d…c394
2 touches
0 conflicts
0x8c9c28de…dbd4
0x065c9d…c394
2 touches
0 conflicts
0x8d882242…dd8a
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity