pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,529,613
← previous block
next block →
recent activity
Analyzing
Block #85,529,613
12 transactions · 11 stateful · 2026-07-04 10:49:34 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,529,613
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
#2
execute
#3
0xaf5e395a
· blocks 1
#4
updatePrices
#6
updatePosition
#7
0x0c7abd22
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x39435dac
#5
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26f952f9…1f04
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x009177df…4ecc
0x34b655…2a6f
2 touches
0 conflicts
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x1ecde41f…f54d
0x34b655…2a6f
2 touches
0 conflicts
0x4347b62a…ed5f
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
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
0x26f952f9df…1f1f04
Audit this contract →
← previous block
·
next block →
recent activity