pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,570,834
← previous block
next block →
recent activity
Analyzing
Block #85,570,834
11 transactions · 11 stateful · 2026-07-04 15:24:03 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,570,834
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#2
0xab083028
#3
updatePrices
#4
0x5a5d9a99
#5
0x0f6795d9
#6
0x0f6795d9
#7
0x0c7abd22
· blocks 1
#9
updateDataFeedsValuesPartial
#10
setData
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb99a324b…a15e
0x065c9d…c394
3 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x776b206d…6cf9
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
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
0x5540f95607…2d69e8
Audit this contract →
← previous block
·
next block →
recent activity