pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,788,253
← previous block
next block →
recent activity
Analyzing
Block #90,788,253
9 transactions · 8 stateful · 2026-07-27 13:51:41 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,788,253
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x2f745df6
#2
0xab083028
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0xf5d05576
#7
setData
#8
exactInputSingle
#5
execFwdPositionOps
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
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0x9211e33e…0b61
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdf303eee…de45
0x34b655…2a6f
4 touches
1 conflict
0xee8237bd…46ad
0x34b655…2a6f
4 touches
1 conflict
0x3397b03f…0849
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x357773b7…8c0e
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:
Perpl
1 conflict on slot
0x7d6b9af162…f89a38
Audit this contract →
← previous block
·
next block →
recent activity