pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,786,301
← previous block
next block →
recent activity
Analyzing
Block #90,786,301
14 transactions · 11 stateful · 2026-07-27 13:41:50 UTC
Parallelism
86
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,786,301
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x6a676095
#3
updatePrices
· blocks 1
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
execFwdPositionOps
· blocks 1
#10
0x3f5c179b
#11
0x3f5c179b
#12
updateDataFeedsValuesPartial
#13
setData
#4
updatePrices
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x00000000…000a
0x0cf3fd…285e
2 touches
0 conflicts
0x00000000…0013
0x0cf3fd…285e
2 touches
0 conflicts
0x00000000…0014
0x0cf3fd…285e
2 touches
0 conflicts
0x00000000…0009
0x32681b…919f
2 touches
0 conflicts
0x00000000…000c
0x32681b…919f
2 touches
0 conflicts
0x0f8a9187…89f4
0x32681b…919f
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity