pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,705,773
← previous block
next block →
recent activity
Analyzing
Block #90,705,773
13 transactions · 13 stateful · 2026-07-27 06:56:44 UTC
Parallelism
77
/100
Blocked
23
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,705,773
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
setPrice
#2
setPrice
#3
setPrice
#4
setPrice
#5
0xab083028
#6
updatePrices
#7
execFwdPositionOps
· blocks 3
#11
setData
#12
execOrders
#8
execFwdPositionOps
#9
execFwdPositionOps
· blocks 1
#10
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfb646d94…aa28
0x34b655…2a6f
4 touches
1 conflict
0x098b0362…866b
0x34b655…2a6f
4 touches
1 conflict
0x09a90ed3…6897
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x91803cbc…2f15
0x34b655…2a6f
4 touches
1 conflict
0x98862f54…62ca
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity