pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,633,428
← previous block
next block →
recent activity
Analyzing
Block #85,633,428
11 transactions · 7 stateful · 2026-07-04 22:20:48 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,633,428
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
0xb29376…4a25
#7
0x9c0d5d…28a5
#8
setData
#9
0xd23880…0eaa
#10
0x2d8c52…4c5e
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x202c03eb…cf33
0xa6afd3…d132
4 touches
1 conflict
0x5c4c05e0…db5d
0xa6afd3…d132
4 touches
1 conflict
0xdec5bfea…d17f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x27c560ea…0923
0xa6afd3…d132
3 touches
1 conflict
0xe63a38b0…1300
0xa6afd3…d132
3 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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-WETH/USDC
1 conflict on slot
0x202c03eb74…a7cf33
Audit this contract →
← previous block
·
next block →
recent activity