pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,274,264
← previous block
next block →
recent activity
Analyzing
Block #90,274,264
11 transactions · 10 stateful · 2026-07-25 18:31:30 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,274,264
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#10
execOrders
#4
execFwdPositionOps
· blocks 1
#5
batchUpdate
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab0760c4…4cfd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0236e3dc…749c
0x34b655…2a6f
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x1c255c26…11dd
0x34b655…2a6f
2 touches
0 conflicts
0x21ed9608…b79b
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
0xab0760c464…554cfd
Audit this contract →
← previous block
·
next block →
recent activity