pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,023,947
← previous block
next block →
recent activity
Analyzing
Block #90,023,947
12 transactions · 12 stateful · 2026-07-24 21:26:55 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,023,947
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
execPerpOps
#4
0x5a5d9a99
#5
0x5a5d9a99
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
· blocks 1
#11
0xc7e3ec2c
#10
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2774c17…b60c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x029eabb6…8d7e
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
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
0xf2774c176d…4fb60c
Audit this contract →
← previous block
·
next block →
recent activity