pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,232,351
← previous block
next block →
recent activity
Analyzing
Block #90,232,351
10 transactions · 9 stateful · 2026-07-25 15:00:15 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,232,351
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x5a5d9a99
#3
0x000000b2
#4
updatePriceFeedsIfNecessary
#5
execFwdPositionOps
· blocks 1
#7
0xed82b078
#8
setData
#9
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x1b244003…c9d0
0x34b655…2a6f
4 touches
1 conflict
0x9816fc81…4f3d
0x34b655…2a6f
4 touches
1 conflict
0xc1aa38d0…a9f3
0x34b655…2a6f
4 touches
1 conflict
0xc467a38b…cf75
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe0c7c055…8db3
0x34b655…2a6f
4 touches
1 conflict
0x0e0a3c1a…f9fb
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
1 conflict on slot
0x4f39448303…4fff62
Audit this contract →
← previous block
·
next block →
recent activity