pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,962,992
← previous block
next block →
recent activity
Analyzing
Block #85,962,992
10 transactions · 7 stateful · 2026-07-06 10:57:23 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,962,992
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#4
0x0f6795d9
#5
0x0f6795d9
#7
setData
#8
0xaeb67f…93f9
#9
0xdfa5ba…0c91
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x12758aef…534b
0x065c9d…c394
2 touches
0 conflicts
0x7cf3370c…4f66
0x065c9d…c394
2 touches
0 conflicts
0x89bdbec6…9ae3
0x065c9d…c394
2 touches
0 conflicts
0xbe9b852e…ddd5
0x065c9d…c394
2 touches
0 conflicts
0xd35bb5ac…3586
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
0xa4f8097941…fd4d71
Audit this contract →
← previous block
·
next block →
recent activity