pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,231,894
← previous block
next block →
recent activity
Analyzing
Block #90,231,894
10 transactions · 8 stateful · 2026-07-25 14:57:57 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,231,894
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x000000b2
#3
execFwdPositionOps
#4
verifyOracleProofV2
#5
0x29eed2d3
· blocks 1
#7
execFwdPositionOps
#8
0x6a64cf6d
#9
setData
#6
0x29eed2d3
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
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x9b03d635…132b
0x928dc8…8207
4 touches
1 conflict
0x0e0a3c1a…f9fb
0x34b655…2a6f
2 touches
0 conflicts
0x34933aba…06e4
0x34b655…2a6f
2 touches
0 conflicts
0x34933aba…06e5
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x87d62b39…b5ab
0x34b655…2a6f
2 touches
0 conflicts
0x94d0ccfd…76d2
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:
USDC (USDC)
1 conflict on slot
0x5311f86450…380984
Audit this contract →
← previous block
·
next block →
recent activity