pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,743,241
← previous block
next block →
recent activity
Analyzing
Block #85,743,241
13 transactions · 9 stateful · 2026-07-05 10:33:23 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,743,241
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x3f5c179b
#3
0x6df9e92b
#4
batchUpdate
#5
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
exactInputSingle
#9
setData
#10
0x240190…f97a
#11
0x4f9410…624d
#12
0xe5f09a…0cec
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x44ad89ba…cf83
0x0a917f…7777
2 touches
0 conflicts
0x8fa7a69c…8fd7
0x0a917f…7777
2 touches
0 conflicts
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0xaeb5864c…7679
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:
Perpl
1 conflict on slot
0x8b305a3b6b…0c1c35
Audit this contract →
← previous block
·
next block →
recent activity