pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,722,200
← previous block
next block →
recent activity
Analyzing
Block #90,722,200
8 transactions · 7 stateful · 2026-07-27 08:19:22 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,722,200
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0x8f518381…ae20
0x34b655…2a6f
4 touches
1 conflict
0xfb24441a…4183
0x34b655…2a6f
4 touches
1 conflict
0x110a671c…e284
0x34b655…2a6f
4 touches
1 conflict
0x9f0aff0b…345e
0x34b655…2a6f
4 touches
1 conflict
0x66067e58…fbec
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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
0x49b0842d79…d10a93
Audit this contract →
← previous block
·
next block →
recent activity