pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,296,503
← previous block
next block →
recent activity
Analyzing
Block #90,296,503
11 transactions · 11 stateful · 2026-07-25 20:24:32 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,296,503
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a651bf7
#2
execFwdPositionOps
· blocks 1
#4
0xed82b078
#5
execFwdPositionOps
#6
handleOps
#7
0x36f359b0
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5250e2f6…9390
0x34b655…2a6f
4 touches
1 conflict
0x149ea1fb…e34a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x10981d9e…6ebc
0x34b655…2a6f
2 touches
0 conflicts
0x12d9d45b…9ca2
0x34b655…2a6f
2 touches
0 conflicts
0x22147832…73ea
0x34b655…2a6f
2 touches
0 conflicts
0x2d651956…12e8
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
0x5250e2f63d…9a9390
Audit this contract →
← previous block
·
next block →
recent activity