pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,538,490
← previous block
next block →
recent activity
Analyzing
Block #85,538,490
10 transactions · 8 stateful · 2026-07-04 11:48:40 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,538,490
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
0x5a5d9a99
#6
0x0f6795d9
· blocks 1
#7
setData
#8
exactInputSingle
#2
0xab083028
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c2acda2…3cde
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x37534430…c68b
0x34b655…2a6f
4 touches
1 conflict
0x663d3288…f460
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2ef3da7a…1ac3
0x40c49f…2af0
2 touches
0 conflicts
0x5ce7d2b3…55a2
0x40c49f…2af0
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
0x8c2acda2da…e23cde
Audit this contract →
← previous block
·
next block →
recent activity