pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,350,833
← previous block
next block →
recent activity
Analyzing
Block #86,350,833
10 transactions · 10 stateful · 2026-07-08 06:06:51 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,350,833
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x785f5745
#4
0x0f6795d9
#6
0x57368ddf
#7
0x5339c59f
#8
0x6a4de972
#9
setData
#5
0x0c7abd22
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
0x95fbac48…9dc0
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5aff3b54…792a
0x065c9d…c394
3 touches
1 conflict
0x1e2e43dd…70d1
0x065c9d…c394
3 touches
1 conflict
0x782fffe7…c2ae
0x065c9d…c394
2 touches
0 conflicts
0xedf2083e…ab63
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x116e7d…d8f1
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
0x95fbac4821…8e9dc0
Audit this contract →
← previous block
·
next block →
recent activity